leadup-security-review — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited leadup-security-review (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
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.
Find security problems in a LeadUp project before they reach production: leaked secrets, weak auth, cross-tenant leakage, exposed databases, unsafe uploads, unverified payments/webhooks, and risky deploy config — reported by severity with fixes. Read-only; never prints secret values.
Trigger phrases: "security review", "check secrets", "is this safe", "audit project for security", "check .env", "payment security", "are we leaking keys", "review auth", "is the admin panel protected".
For general "what's left in this repo" (not security) → use leadup-existing-repo-analyzer. For deploy readiness (which includes a lightweight security gate) → leadup-deploy-checker.
.env values — key names only).Use references/security-rules.md. Optional helper: scripts/scan_secrets.py (read-only regex sweep; redacts values).
security-rules.md). Report path:line with the value redacted. Check .gitignore covers .env*.
admin endpoints; session/JWT handling sane.
cross-tenant access (LeadUp SaaS pattern).
server-side; idempotency; never trust client price/status.
fix.
See references/security-rules.md. Most relevant here:
path:line only.trigger phrases.
leadup-existing-repo-analyzer.
scripts/scan_secrets.py locally or apply themanual checklist from security-rules.md.
SECURITY.md/.gitignore as findings.
fail, note as inconclusive — never weaken controls to test.
rzp_live_... key → flagged Critical with valueredacted and rotation steps; the key value is never printed.
High with the file location.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.