Open source · Apache-2.0
Which vulnerable dependencies can an attacker actually reach?
Lockfile scanners report every advisory in your tree. Sage 7 Scan traces imports from your routes and handlers, so the few findings that are really exposed stand apart from the noise. One file, zero dependencies, a few seconds per run.
Run it now
From your project root. No account, no install, no config. Only package names and versions leave your machine (to OSV.dev).
npx @sage7/scan
- T0
- Direct Public Handler. Reached from an HTTP route or entry point. Fix first.
- T1
- Internal Helper. Imported by your application code. Fix soon.
- T2
- Unused Dependency. In the lockfile, never imported. Remove it.
- T3
- Dev Only. Tests, scripts and build tooling. Low priority.
Add it to every pull request
The GitHub Action posts one comment with real-risk vs noise counts and keeps it up to date on every push. Add upload-sarif: true to send results to Code Scanning.
name: Sage 7 Scan
on:
pull_request:
push:
branches: [main]
permissions:
contents: read
pull-requests: write
jobs:
scan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: Genie-Research-Foundation/sage7-scan@v1
with:
fail-on: t0See your results in the Sage 7 dashboard
Scanning needs no account. To keep every scan, track findings over time and see them next to your audits, connect the scanner to a Sage 7 project with a project token.
- 1Create your free Sage 7 accountSign up at sage7.dev and create a project for the app you scan. A Quick audit project is enough.
- 2Create a project tokenIn the project, open Connect Agent and click Create project token. It's shown once: store it as
SAGE7_PROJECT_TOKENin your shell or as a GitHub Actions secret. - 3Run the scan with the tokenThe CLI and the Action send the findings to that project. Without a token nothing is sent to Sage 7.
- 4Open your audit dashboardIn the project, switch to Audit → Security. Every upload is under Scans & tools, and its findings, with T0–T3 reachability, under Findings, next to your audits.
npx @sage7/scan --token $SAGE7_PROJECT_TOKEN
- uses: Genie-Research-Foundation/sage7-scan@v1
with:
fail-on: t0
sage7-token: ${{ secrets.SAGE7_PROJECT_TOKEN }}Show it in your README
[](https://github.com/Genie-Research-Foundation/sage7-scan)
Dependencies are one layer
Sage 7 audits the whole app your AI agents build: architecture drift against your blueprint, security and compliance gaps, and what's actually built versus what was claimed.
Get the full audit