route-scanning — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited route-scanning (Agent Skill) and scored it 45/100 (orange). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 1 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Discover all API route definitions in Express.js source files.
Execute the scanning script:
python3 scripts/scan-routes.py <source_directory>The script outputs a structured route list with method, path, file, and line number.
For each discovered route, also identify:
router.route())Return a JSON-compatible route manifest:
[
{
"method": "GET",
"path": "/api/products",
"file": "src/routes/products.js",
"line": 8,
"middleware": ["requireAuth"],
"type": "standard"
}
]This manifest will be consumed by the next pipeline stage (doc-writing).
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.