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.
1 critical finding reported by osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- mcp_llama
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
7 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 · 0.6s
v2.0.11
3 findings · 7.1s
v0.3.74
8 findings · 1.0s
v0.1.0
0 findings · 3.5s
v0.1.0
0 findings · 3.5s
v0.71.0
60 findings · 0.3s
v2.3.8
74 findings · 7.9s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
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
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 | Flagged42 | — | agentshield: completecisco-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 145 findings across every scanner that examined this package. None of the 1 finding rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 2 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
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.
2 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: AAK-AGENT-002, TOOL_ABUSE_UNDECLARED_NETWORK · Files: CLAUDE.md, /repo/repo/CLAUDE.md · reported by agent-audit-kit, cisco-skill-scanner
The model could have called any of these a false positive and did not.
2 AAK-ANTHROPIC-SDK-001
Files: src/mcp_client.py, src/mcp_llama_agent.py · reported by agent-audit-kit
1 AAK-DNS-REBIND-002
Files: requirements.txt · reported by agent-audit-kit
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: requirements.txt · reported by agent-audit-kit
1 AAK-MCP-SSRF-001
Files: src/weather_mcp_server.py · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: requirements.txt · reported by agent-audit-kit
1 CVE-2025-53643
Files: requirements.txt · reported by trivy
1 CVE-2025-54121
Files: requirements.txt · reported by trivy
1 CVE-2025-62727
Files: requirements.txt · reported by trivy
1 CVE-2025-66416
Files: requirements.txt · reported by trivy
1 CVE-2025-66418
Files: requirements.txt · reported by trivy
1 CVE-2025-66471
Files: requirements.txt · reported by trivy
1 CVE-2025-69223
Files: requirements.txt · reported by trivy
1 CVE-2025-69224
Files: requirements.txt · reported by trivy
1 CVE-2025-69225
Files: requirements.txt · reported by trivy
1 CVE-2025-69226
Files: requirements.txt · reported by trivy
1 CVE-2025-69227
Files: requirements.txt · reported by trivy
1 CVE-2025-69228
Files: requirements.txt · reported by trivy
1 CVE-2025-69229
Files: requirements.txt · reported by trivy
1 CVE-2025-69230
Files: requirements.txt · reported by trivy
1 CVE-2026-21441
Files: requirements.txt · reported by trivy
1 CVE-2026-22815
Files: requirements.txt · reported by trivy
1 CVE-2026-24486
Files: requirements.txt · reported by trivy
1 CVE-2026-25645
Files: requirements.txt · reported by trivy
1 CVE-2026-28684
Files: requirements.txt · reported by trivy
1 CVE-2026-34513
Files: requirements.txt · reported by trivy
1 CVE-2026-34514
Files: requirements.txt · reported by trivy
1 CVE-2026-34515
Files: requirements.txt · reported by trivy
1 CVE-2026-34516
Files: requirements.txt · reported by trivy
1 CVE-2026-34517
Files: requirements.txt · reported by trivy
1 CVE-2026-34518
Files: requirements.txt · reported by trivy
1 CVE-2026-34519
Files: requirements.txt · reported by trivy
1 CVE-2026-34520
Files: requirements.txt · reported by trivy
1 CVE-2026-34525
Files: requirements.txt · reported by trivy
1 CVE-2026-34993
Files: requirements.txt · reported by trivy
1 CVE-2026-40347
Files: requirements.txt · reported by trivy
1 CVE-2026-41066
Files: requirements.txt · reported by trivy
1 CVE-2026-42561
Files: requirements.txt · reported by trivy
1 CVE-2026-44431
Files: requirements.txt · reported by trivy
1 CVE-2026-45409
Files: requirements.txt · reported by trivy
1 CVE-2026-47265
Files: requirements.txt · reported by trivy
1 CVE-2026-48710
Files: requirements.txt · reported by trivy
1 CVE-2026-48817
Files: requirements.txt · reported by trivy
1 CVE-2026-48818
Files: requirements.txt · reported by trivy
1 CVE-2026-49476
Files: requirements.txt · reported by trivy
1 CVE-2026-49477
Files: requirements.txt · reported by trivy
1 CVE-2026-50269
Files: requirements.txt · reported by trivy
1 CVE-2026-52869
Files: requirements.txt · reported by trivy
1 CVE-2026-53537
Files: requirements.txt · reported by trivy
1 CVE-2026-53538
Files: requirements.txt · reported by trivy
1 CVE-2026-53539
Files: requirements.txt · reported by trivy
1 CVE-2026-53540
Files: requirements.txt · reported by trivy
1 CVE-2026-54273
Files: requirements.txt · reported by trivy
1 CVE-2026-54274
Files: requirements.txt · reported by trivy
1 CVE-2026-54275
Files: requirements.txt · reported by trivy
1 CVE-2026-54276
Files: requirements.txt · reported by trivy
1 CVE-2026-54277
Files: requirements.txt · reported by trivy
1 CVE-2026-54278
Files: requirements.txt · reported by trivy
1 CVE-2026-54279
Files: requirements.txt · reported by trivy
1 CVE-2026-54280
Files: requirements.txt · reported by trivy
1 CVE-2026-54282
Files: requirements.txt · reported by trivy
1 CVE-2026-54283
Files: requirements.txt · reported by trivy
1 CVE-2026-59881
Files: requirements.txt · reported by trivy
1 CVE-2026-59950
Files: requirements.txt · reported by trivy
1 CVE-2026-69243
Files: requirements.txt · reported by trivy
1 CVE-2026-69244
Files: requirements.txt · reported by trivy
1 GHSA-27v5-c462-wpq7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-345p-7cg4-v4c7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6fg3-hvw7-2fwq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7mvr-c777-76hp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8r9q-7v3j-jr4g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w48q-cv73-mx4w
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wqch-xfxh-vrr4
Files: /repo/package-lock.json · reported by osv-scanner
1 PYSEC-2026-1097
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1099
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1100
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1101
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1104
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1105
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1106
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1107
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1109
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1617
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1852
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1941
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1942
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1994
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1996
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1998
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2094
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2095
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2096
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2097
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2098
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2099
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2100
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2101
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2102
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2103
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2104
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2105
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2106
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2107
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2108
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2109
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2110
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2111
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2112
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2113
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-237
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3037
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3038
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3039
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3040
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3041
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3071
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3072
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3545
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3546
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3547
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-87
Files: /repo/requirements.txt · reported by osv-scanner
2 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/SKILL.md · reported by cisco-skill-scanner
Critical vulnerability and multiple high-severity issues found.
A critical vulnerability (PYSEC-2026-2102) exists in a dependency listed in `/repo/requirements.txt`, which could enable remote code execution. Additionally, multiple high-severity vulnerabilities are present in other dependencies across `requirements.txt` and `package-lock.json`. The artifact's code in `src/mcp_client.py` and `src/mcp_llama_agent.py` interacts with the Anthropic SDK, and a high-severity DNS rebind vulnerability (AAK-DNS-REBIND-002) is noted in `requirements.txt`. These findings indicate potential for network egress or credential access.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 61; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.