shadows-deploy-guardian@1.1.0
CAUTION· static onlyPublisher claims: "Pre-deployment verification checklist — tests, types, build, secrets scan, environment validation. Use before pushing to production or staging." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-20 and scored it 62/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
git ls-files | grep -E "\.env$|\.env\.\w+" | head -10Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- [ ] Zero `.env` files tracked by gitFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.COVERAGE=$(grep -cE "\.env|secret|credential|\.pem|\.key" .gitignore)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Check .env files not committed to gitFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.[ -f tsconfig.json ] && npx tsc --noEmit 2>&1Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
18 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim nakedoshadow: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.