Is Veto safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highShell command built from a string (injection risk)
Public scan report
scanner v0.1.3 · 2026-09-19 · same rubric, same numbers if you re-run it
1 high1 medium
- Code scan318 source files scanned8/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (2)
- mediumeval / new Function used
exec.evaldist/agents/security/penetration.js: …turn no data or 400, not 500', 'eval() and shell execution with user input ar…
- highShell command built from a string (injection risk)
exec.shell-concatdist/memory/local.js: …n`. See VETO_DB_SCHEMA_VERSION. _db.exec(`PRAGMA user_version = ${VETO_DB_SCHEMA_VERSION}`); return _d…
Overall 63/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON