scan — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited scan (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
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.
Show the user the latest output of ai-security-scan, which runs automatically on every deploy and writes its JSON to /home/ubuntu/security_scan.json. Renders a score, per-severity counts, and top findings.
echo "$NOMETRIA_API_KEY"
echo "$NOMETRIA_TOKEN"
grep -s 'NOMETRIA_API_KEY\|NOMETRIA_TOKEN' .env .env.local 2>/dev/null
cat ~/.nometria/credentials.json 2>/dev/nullIf no token: tell the user to run /login. Stop.
Store: TOKEN="<the token>"
cat nometria.json 2>/dev/nullIf absent, use $ARGUMENTS or list migrations:
curl -s -X POST https://app.nometria.com/listUserMigrations \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $TOKEN" \
-d '{}'Store: APP_ID="<app_id>".
curl -s -X POST https://app.nometria.com/getSecurityScan \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $TOKEN" \
-d "{\"app_id\": \"$APP_ID\"}"Response shape:
{
"scan": {
"passed": false,
"scanned_files": 142,
"summary": { "critical": 1, "high": 3, "medium": 5, "low": 2, "total": 11 },
"findings": [
{ "rule_id": "SEC-001", "severity": "CRITICAL", "file": "src/api.js", "line": 42,
"message": "Hardcoded API key", "snippet": "...", "fix": "..." }
]
},
"status": "ok"
}If status === "no_scan_yet" - tell the user no scan has run yet on this app and suggest triggering a deploy. Stop.
Score (0-100) = 100 − (critical × 25) − (high × 10) − (medium × 3) − (low × 1), clamped to [0,100].
Display:
Security Score: 72/100
CRITICAL: 1 HIGH: 3 MEDIUM: 5 LOW: 2
Total findings: 11 Scanned files: 142List the top 5 findings (sorted by severity, then file). For each:
[CRITICAL] SEC-001 - Hardcoded API key
src/api.js:42
Fix: Move the key to .env and reference via process.env.API_KEYpip install ai-security-scan && security-scan .Do all of the above. Execute the curl call and report results to the user.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.