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 -- mcp_in_golang
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 · 9.0s
v0.3.74
0 findings · 1.2s
v0.1.0
0 findings · 5.1s
v0.1.0
0 findings · 5.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged50 | — | 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 · 4.0s
v0.71.0
15 findings · 0.2s
v2.3.8
65 findings · 0.8s
vv1.6.0
Incomplete run
0 findings · 1.7s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.3s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 0.9s
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 Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 82 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 53 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 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-4013
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-4340
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4342
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-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-4980
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4982
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4986
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5025
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5030
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5037
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5777
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6088
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6090
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6091
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6218
Files: /repo/go.mod · reported by osv-scanner
52 The model's answer could not be read.
Rules: CVE-2026-33252, GO-2026-4569, CVE-2026-27896 and 47 more · Files: go.mod, /repo/go.mod, /repo/SKILL.md · reported by trivy, 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
Multiple high-severity vulnerabilities in dependencies
This artifact contains multiple high-severity vulnerabilities identified in its declared dependencies. These vulnerabilities, found in the `go.mod` file, could potentially lead to various security risks depending on the specific component and its usage. Reviewing the identified CVEs and GHSAs is recommended to understand the potential impact on network egress, shell execution, credential access, or file writes.
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.