Loading the registry…
Add your description here
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 -- nccn-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 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
3 findings · 8.0s
v0.3.74
7 findings · 1.6s
v0.1.0
0 findings · 3.7s
v0.1.0
0 findings · 3.7s
v0.71.0
60 findings · 0.3s
v2.3.8
61 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.3s
vv0.3.2
No Go packages 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 · 2.2s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged43 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | 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 131 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 104 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-22690
Files: uv.lock · reported by trivy
1 CVE-2026-22691
Files: uv.lock · reported by trivy
1 CVE-2026-24688
Files: uv.lock · reported by trivy
1 CVE-2026-27628
Files: uv.lock · reported by trivy
1 CVE-2026-28804
Files: uv.lock · reported by trivy
1 CVE-2026-4539
Files: uv.lock · reported by trivy
1 CVE-2026-48155
Files: uv.lock · reported by trivy
1 CVE-2026-48710
Files: uv.lock · reported by trivy
1 CVE-2026-53537
Files: uv.lock · reported by trivy
1 CVE-2026-53538
Files: uv.lock · reported by trivy
1 CVE-2026-53540
Files: uv.lock · reported by trivy
1 CVE-2026-54282
Files: uv.lock · reported by trivy
1 GHSA-jm82-fx9c-mx94
Files: uv.lock · reported by trivy
1 PYSEC-2026-1828
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1829
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1832
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2987
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3005
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3010
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3013
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3016
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3021
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3023
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3037
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3040
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3041
Files: /repo/uv.lock · reported by osv-scanner
101 The model's answer could not be read.
Rules: AAK-MCP-SDK-CVE-2026-52869-001, PYSEC-2026-2401, PYSEC-2026-1942 and 95 more · Files: pyproject.toml, uv.lock, /repo/uv.lock and 3 more · reported by agent-audit-kit, osv-scanner, trivy and 1 more
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: SECURITY.md, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
Artifact contains critical vulnerabilities and sensitive code patterns.
The artifact includes multiple high-severity vulnerabilities in its dependencies, which could lead to remote code execution or privilege escalation. Additionally, the installed code in `/repo/nccn_get_index.py` exhibits sensitive patterns that warrant attention. A specific high-severity vulnerability (AAK-MCP-SDK-CVE-2026-52869-001) is present in an included SDK. These findings indicate potential for unauthorized system access or data compromise.
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.
Showing 23 of 23; the rest are in the per-scanner reports above.