GitHub Dependabot — free
Keep this one.
Continuous alerts for known vulnerable dependencies across every repo, from GitHub, for $0. That's the only scanner you need — because the other kind of checking moves inside the Job.
Compare
Do you still need Semgrep?
No. Static analysis runs inside every FalseGreen Job on the exact source — and findings gate acceptance instead of waiting for someone to read a report.
What Semgrep does
What it does well.
- Excellent open-source SAST engine and rule ecosystem
- Fast, custom rules you can write yourself
- Platform dashboards and enforcement for large fleets
The replacement
Free Dependabot + one FalseGreen Job covers Semgrep.
FalseGreen Job — before merge
This replaces Semgrep.
Static analysis becomes part of the acceptance decision instead of a tool your team triages.
The feature matrix
FalseGreen vs Semgrep, line by line.
| Capability | FalseGreen | Semgrep |
|---|---|---|
| Primary purposeThe main problem the product is designed to solve. | Independent whole-program acceptance | Code security and static analysis |
| Dedicated security or static analysisSpecialized analysis for code quality, vulnerabilities, or security findings. | ✓ Yes | ✓ Yes |
| Frozen human-defined definition of doneThe frozen acceptance target is established before implementation is judged. | ✓ Yes | ◐ Partial |
| Frozen Job target preserved through repairThe agreed Job target remains authoritative while the implementation is repaired and reverified. | ✓ Yes | ◐ Partial |
| Separate Job acceptance authorityA distinct authority decides whether the FalseGreen Job is accepted. | ✓ Yes | — Not primary |
| Job or outcome-level acceptanceAnswers whether the whole program meets the agreed definition of done. | ✓ Yes | — Not primary |
| Exact-source-bound acceptanceAcceptance belongs explicitly to the exact source state that earned it. | ✓ Yes | ◐ Partial |
| Repair against unchanged requirementsRepairs can be reverified while the original acceptance target remains frozen. | ✓ Yes | ◐ Partial |
| Heterogeneous evidence for acceptanceTests, CI, scanners, formal tools, behavior, and inspection can inform one Job decision. | ✓ Yes | ◐ Partial |
| Explicit verdictReturns Accepted, Failed, or Insufficient Evidence for the verified program. | ✓ Yes | ◐ Partial |
| Re-checkable evidence and limitationsPreserves what was checked, the relevant source, supporting evidence, and limitations. | ✓ Yes | ◐ Partial |
FalseGreen
- Primary purpose
- Independent whole-program acceptance
- Dedicated security or static analysis
- ✓ Yes
- Frozen human-defined definition of done
- ✓ Yes
- Frozen Job target preserved through repair
- ✓ Yes
- Separate Job acceptance authority
- ✓ Yes
- Job or outcome-level acceptance
- ✓ Yes
- Exact-source-bound acceptance
- ✓ Yes
- Repair against unchanged requirements
- ✓ Yes
- Heterogeneous evidence for acceptance
- ✓ Yes
- Explicit verdict
- ✓ Yes
- Re-checkable evidence and limitations
- ✓ Yes
Semgrep
- Primary purpose
- Code security and static analysis
- Dedicated security or static analysis
- ✓ Yes
- Frozen human-defined definition of done
- ◐ Partial
- Frozen Job target preserved through repair
- ◐ Partial
- Separate Job acceptance authority
- — Not primary
- Job or outcome-level acceptance
- — Not primary
- Exact-source-bound acceptance
- ◐ Partial
- Repair against unchanged requirements
- ◐ Partial
- Heterogeneous evidence for acceptance
- ◐ Partial
- Explicit verdict
- ◐ Partial
- Re-checkable evidence and limitations
- ◐ Partial
Also comparing