scancode-next: Deploy SAST tools as scheduled CI jobs across AboutCode repositories

Open
#320 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions
Domain
ci-cd, security

Research direction

Start by identifying the AboutCode repositories and their existing CI configuration, then choose an open source SAST tool suitable for each project. Add scheduled CI jobs, run them to collect initial findings, and triage high severity results. Done means the jobs run on a schedule and high severity findings are fixed or documented, with exclusion rules updated where needed.

Written by the indexing model from the issue text.

Description

maintainers-only

Deploy open source code linters, SAST (Static Application Security Testing) tools for each project; run them on a schedule in CI, triage the first results; fix or document high-severity findings, updating SAST exclusion rules as needed.

These can be open source or CodeQL-based, proprietary tools.

This also covers other security checks deployment and automation

Dominant language
Batchfile
Stars
316
Forks
257
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/aboutcode

All issues in aboutcode-org/aboutcode

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.