The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
github_release: https://github.com/cyberlife-coder/VelesDB, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- VelesDB
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 3.2s
v2.0.11
Timed out
0 findings · 300.0s
v0.3.26
Timed out
0 findings · 300.0s
v0.1.0
4 findings · 74.3s
v0.1.0
3 findings · 74.3s
v0.1.0
0 findings · 35.4s
v0.71.0
2 findings · 8.5s
v2.3.8
1 finding · 22.3s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
No report in this scan: capslock, govulncheck.
3 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 3, 2026 | Flagged84 | — | agentshield: completecisco-skill-scanner ·!: timeoutagent-audit-kit ·!: timeoutnerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·n/a: not applicable | completed |
| Jul 30, 2026 | Scan Halted | — | cisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: complete | rejected |
| Jul 30, 2026 | Scan Halted | — | cisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: complete | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 10 findings across every scanner that examined this package.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
1 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: GHSA-wrw7-89jp-8q8g · Files: demos/tauri-rag-app/src-tauri/Cargo.lock · reported by trivy
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
4 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/sdks/typescript/src/backends/crud-backend.ts, /repo/sdks/typescript/src/backends/streaming-backend.ts, /repo/sdks/typescript/src/embed.ts · reported by nerlo-behavioral
2 opt.nerlo-rules.nerlo-install-run-bundled-artifact
Files: /repo/integrations/agent-hooks/README.md, /repo/integrations/agent-hooks/codex/README.md · reported by nerlo-install-instruction
1 GHSA-wrw7-89jp-8q8g
Files: Cargo.lock · reported by trivy
1 opt.nerlo-rules.nerlo-install-pipe-to-shell
Files: /repo/CHANGELOG.md · reported by nerlo-install-instruction
1 PYSEC-2026-2275
Files: /repo/benchmarks/requirements.txt · reported by osv-scanner
Artifact enables network egress and shell execution.
The artifact's installed code includes multiple instances of potential secret exposure leading to network egress in TypeScript backend files and an embed script. Its installation instructions also involve piping directly to a shell, which can execute arbitrary commands. Additionally, the artifact contains known vulnerabilities in bundled dependencies.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.