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.
7 critical findings reported by trivy, 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 -- fastmpc
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
4 findings · 7.7s
v0.3.74
2 findings · 1.2s
v0.1.0
0 findings · 3.5s
v0.1.0
0 findings · 3.5s
v0.71.0
68 findings · 0.3s
v2.3.8
69 findings · 1.5s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
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.9s
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 | Flagged45 | — | 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 143 findings across every scanner that examined this package. None of the 7 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 79 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.
2 CVE-2026-45134
Files: uv.lock · reported by trivy
2 GHSA-rcfx-77hg-w2wv
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
1 CVE-2025-59420
Files: uv.lock · reported by trivy
1 CVE-2025-61920
Files: uv.lock · reported by trivy
1 CVE-2025-64340
Files: uv.lock · reported by trivy
1 CVE-2025-66471
Files: uv.lock · reported by trivy
1 CVE-2025-68664
Files: uv.lock · reported by trivy
1 CVE-2025-69196
Files: uv.lock · reported by trivy
1 CVE-2026-23490
Files: uv.lock · reported by trivy
1 CVE-2026-24486
Files: uv.lock · reported by trivy
1 CVE-2026-25528
Files: uv.lock · reported by trivy
1 CVE-2026-25645
Files: uv.lock · reported by trivy
1 CVE-2026-26007
Files: uv.lock · reported by trivy
1 CVE-2026-26013
Files: uv.lock · reported by trivy
1 CVE-2026-27124
Files: uv.lock · reported by trivy
1 CVE-2026-27962
Files: uv.lock · reported by trivy
1 CVE-2026-28684
Files: uv.lock · reported by trivy
1 CVE-2026-32871
Files: uv.lock · reported by trivy
1 CVE-2026-34073
Files: uv.lock · reported by trivy
1 CVE-2026-40347
Files: uv.lock · reported by trivy
1 CVE-2026-41481
Files: uv.lock · reported by trivy
1 CVE-2026-44431
Files: uv.lock · reported by trivy
1 CVE-2026-4539
Files: uv.lock · reported by trivy
1 CVE-2026-48710
Files: uv.lock · reported by trivy
1 CVE-2026-48818
Files: uv.lock · reported by trivy
1 CVE-2026-52869
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 CVE-2026-55443
Files: uv.lock · reported by trivy
1 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/src/services/http/http_client.py · reported by cisco-skill-scanner
1 GHSA-c2jp-c369-7pvx
Files: uv.lock · reported by trivy
1 GHSA-f4xh-w4cj-qxq8
Files: uv.lock · reported by trivy
1 PYSEC-2026-107
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1202
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1364
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1518
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1617
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1942
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2116
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2119
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2193
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2474
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2475
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2476
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2562
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2563
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2582
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2583
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2584
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-287
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2987
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
1 PYSEC-2026-338
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-36
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-373
Files: /repo/uv.lock · reported by osv-scanner
75 The model's answer could not be read.
Rules: CVE-2025-66418, PYSEC-2026-2117, GHSA-537c-gmf6-5ccf and 71 more · Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner, agent-audit-kit
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: TOOL_ABUSE_UNDECLARED_NETWORK, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/repo/README.md, /repo/SKILL.md · reported by cisco-skill-scanner
1 The model did not answer for these findings.
Rules: PYSEC-2026-1994 · Files: /repo/uv.lock · reported by osv-scanner
Critical vulnerabilities detected in installed code dependencies.
The artifact contains critical vulnerabilities, including multiple PYSEC and CVEs, primarily affecting dependencies specified in `uv.lock`. These issues may enable various impacts such as server-side request forgery (SSRF) and other remote code execution vectors. Attention is warranted due to the potential for unauthorized network egress and system compromise.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 83; 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.