Guides

Pre-merge security checklist

Updated 2026-11-17

Short answer

Before you merge a pull request, check that the change adds no new security flaw, no vulnerable dependency, no secret and no risky infrastructure setting. The eight checks below can all be automated.

The checklist

  1. Scan only what changed, so new findings are not buried under old ones.
  2. Follow user input: does any new code send it to a query, a command, a template or a file path?
  3. Look at new dependencies: known vulnerabilities, licence and whether they are maintained.
  4. Look for secrets in the diff, including in tests and examples.
  5. Review changes to Dockerfiles, Kubernetes manifests and Terraform.
  6. Check that new endpoints require authentication.
  7. If you suppress a finding, record why, who decided and until when.
  8. Fix what can be reached from outside first.

How scancodebase helps

scancodebase reports only what is new in each pull request, shows the path the data takes for every finding and proposes a fix. Suppressions carry a reason, an owner and an expiry date.

More guides

Scan yours before the next merge.