Features

Your own rules Your codebase, your rules

scancodebase lets you add rules for the patterns that matter in your own code, written with a syntax compatible with Semgrep.

What it finds

  • Internal functions that must never receive user input
  • Deprecated calls your team has agreed to stop using
  • Patterns from a past incident, so it does not happen twice

What you get

  • Rules that run next to the built-in ones in every scan
  • A new rule asked against code already scanned, without scanning it again
  • Suppressions in the code or in a file, each with a reason, an owner and an expiry date
  • Metrics by repository and by team

What makes it different

Code that has already been analysed is not analysed again, so adding a rule gives you an answer across the whole codebase quickly.

Which plan includes it

Captain and above. Compare plans.

FAQ

Questions about this feature

Can I reuse existing Semgrep rules?

The rule syntax is compatible with Semgrep, so existing rules are a good starting point.

What happens when a suppression expires?

The finding is reported again, so a temporary exception does not become permanent by accident.

More features

Scan yours before the next merge.