We took a real Django app with 50 intentional vulnerabilities planted across 5 difficulty tiers.
We ran every popular security tool with its default out-of-box setup — exactly how a developer
would install and run them. No custom rules. No flags. No configuration.
Then we ran stageclear scan .
Here is what happened.
| TOOL | RAW OUTPUT | UNIQUE VULNS FOUND | NOISE / FP RATE | STATUS |
|---|---|---|---|---|
| Bandit | 18 findings | 9 real | 50% noise | Runs |
| Ruff (security) | 15 findings | 9 real | 40% noise | Runs |
| Semgrep auto | 28 findings | ~22 real | 21% noise | Runs |
| Bearer | 25 findings | 24 real | 4% noise | Runs |
| Safety | 110 findings | 5 packages | 0% but 22× inflated | Runs |
| OSV-Scanner | 111 findings | 8 packages | 0% but duplicated | Runs |
| Gitleaks | 0 findings | 0 real | — | ✗ FAILED |
| detect-secrets | 6 findings | 2 real | 67% false positive | Runs* |
| pip-audit | — | 0 | — | ✗ FAILED |
| stageclear scan . | 77 findings | 39/50 vulns | 2.6% false positive | ✓ WORKS |
* detect-secrets requires --all-files flag; without it finds 0. Gitleaks fails silently on non-git directories.
Free runs all 11 open-source scanners with their default detection rules — exactly what you'd get doing it yourself, in one command.
Pro adds 569 custom detection rules built for real attack patterns default tools never see — plus deduplication, baselines, and CI integration.
| WHAT YOU GET | FREE | ★ PRO |
|---|---|---|
| Detection rules | default rules only | +569 custom rules |
| Duplicate findings from 9 tools collapsed into one | ✗ | ✓ |
| 569 custom rules (Django / Flask / FastAPI / aiohttp / Tornado / more) | ✗ | ✓ |
| DEBUG=True, ALLOWED_HOSTS=*, missing middleware detection | ✗ | ✓ |
| Baseline: only show findings newer than last commit | ✗ | ✓ |
| SARIF output for GitHub / Jira / Linear | ✗ | ✓ |
| CI/CD: block deploy on new criticals | ✗ | ✓ |
| False positive rate | ~25% (Semgrep default) | 2.6% with dedup + custom rules |
| T1–T3 vulnerability coverage (out of 30) | ~50% default rules | 97% with +569 custom rules |
| Hardcoded secrets: SECRET_KEY, DB passwords caught | ✗ default tools miss these | ✓ |
| Rule update feed | ✗ | ✓ new rules as threats emerge |