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.
3 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 -- illustrator
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 · 6.7s
v0.3.74
4 findings · 1.1s
v0.1.0
0 findings · 2.7s
v0.1.0
0 findings · 2.7s
v0.71.0
63 findings · 0.2s
v2.3.8
32 findings · 1.3s
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.7s
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 103 findings across every scanner that examined this package. None of the 3 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 3 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 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml, uv.lock · reported by agent-audit-kit
2 CVE-2025-43859
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-53365
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-53366
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-54121
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-62727
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-66416
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-25990
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-40192
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-42308
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-42310
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-42311
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-45409
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48710
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48817
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48818
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-52869
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-54058
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-54059
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-54060
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-54282
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-54283
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-55379
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-55380
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-55798
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59197
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59198
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59199
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59200
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59204
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59205
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59950
Files: requirements.txt, uv.lock · reported by trivy
1 AAK-DNS-REBIND-002
Files: pyproject.toml · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: pyproject.toml · reported by agent-audit-kit
1 BINARY_FILE_DETECTED
Files: /repo/requirements.txt · reported by cisco-skill-scanner
1 CVE-2026-28684
Files: requirements.txt · reported by trivy
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1616
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1617
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1618
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-165
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1941
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1942
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2250
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2252
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2253
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2254
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2255
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2257
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2874
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3451
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3453
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3454
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-348
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3493
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3494
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3495
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3496
Files: /repo/uv.lock · reported by osv-scanner
1 UNANALYZABLE_BINARY
Files: /repo/requirements.txt · reported by cisco-skill-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
1 The model did not answer for these findings.
Rules: PYSEC-2026-2256 · Files: /repo/uv.lock · reported by osv-scanner
Critical vulnerabilities found in artifact dependencies
The artifact contains critical and high severity vulnerabilities within its dependencies, identified in `requirements.txt`, `uv.lock`, and `pyproject.toml`. Critical findings, including CVE-2025-43859 and PYSEC-2026-348, indicate potential for severe impact such as remote code execution or data compromise. Additionally, a high severity DNS rebinding vulnerability (AAK-DNS-REBIND-002) is present, which could facilitate unauthorized network access. Numerous other high severity vulnerabilities also warrant attention.
Concern level assessed by the review: Critical. 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 25 of 70; the rest are in the per-scanner reports above.