Loading the registry…
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- gerrit-mcp
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.
v2.0.11
2 findings · 7.9s
v0.3.74
0 findings · 0.8s
v0.1.0
0 findings · 3.5s
v0.1.0
0 findings · 3.5s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Caution86 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·!: incompletenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicable |
vv0.3.2
Incomplete run
0 findings · 1.5s
v0.71.0
1 finding · 0.2s
v2.3.8
48 findings · 0.9s
vv1.6.0
Incomplete run
0 findings · 1.4s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.0s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
| completed |
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 Caution badge are computed from those raw severities alone. Nothing below moved them.
Out of 51 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 26 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
1 CVE-2026-32285
Files: go.mod · reported by trivy
1 GO-2025-3956
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4006
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4007
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4009
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4012
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4015
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4155
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4337
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4342
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4514
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4864
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4865
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4869
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4918
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4946
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4947
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4970
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4971
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4976
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4977
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4982
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5037
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6088
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6218
Files: /repo/go.mod · reported by osv-scanner
25 The model's answer could not be read.
Rules: GO-2026-6090, GO-2025-4013, GO-2026-4340 and 22 more · Files: /repo/go.mod, /repo/SKILL.md · reported by osv-scanner, cisco-skill-scanner
1 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION · Files: /repo/SKILL.md · reported by cisco-skill-scanner
High-severity vulnerabilities and potential credential exposure identified.
The artifact contains high-severity vulnerabilities in its dependencies, as indicated by findings in `go.mod`. Additionally, a high-severity finding points to potential credential access within `/repo/pkg/mcp/config.go`. These issues warrant attention due to risks related to supply chain security and sensitive information handling.
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.