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.
5 critical findings 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 -- my-turborepo
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
12 findings · 8.5s
v0.3.74
5 findings · 2.4s
v0.1.0
0 findings · 3.4s
v0.1.0
0 findings · 3.4s
v0.71.0
148 findings · 0.4s
v2.3.8
296 findings · 9.3s
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.1s
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 | Flagged47 | — | 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 461 findings across every scanner that examined this package. None of the 5 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 385 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.
4 GHSA-42h9-826w-cgv3
Files: /repo/package-lock.json, /repo/yarn.lock, package-lock.json and 1 more · reported by osv-scanner, trivy
3 CVE-2026-12590
Files: apps/mcp-server/yarn.lock, package-lock.json, yarn.lock · reported by trivy
3 CVE-2026-2391
Files: apps/mcp-server/yarn.lock, package-lock.json, yarn.lock · reported by trivy
3 GHSA-38r7-794h-5758
Files: /repo/apps/mcp-server/yarn.lock, /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
3 GHSA-4x5r-pxfx-6jf8
Files: /repo/apps/mcp-server/yarn.lock, /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
3 GHSA-52f5-9888-hmc6
Files: /repo/apps/mcp-server/yarn.lock, /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
3 GHSA-73rr-hh4g-fpgx
Files: /repo/apps/mcp-server/yarn.lock, /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
3 GHSA-8fgc-7cc6-rx7x
Files: /repo/apps/mcp-server/yarn.lock, /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
3 GHSA-v422-hmwv-36x6
Files: /repo/apps/mcp-server/yarn.lock, /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
3 GHSA-w7fw-mjwx-w883
Files: /repo/apps/mcp-server/yarn.lock, /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
3 GHSA-xffm-g5w8-qvg7
Files: /repo/apps/mcp-server/yarn.lock, /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 CVE-2025-13465
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2025-56200
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2025-69873
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-2950
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-33750
Files: yarn.lock · reported by trivy
2 CVE-2026-40175
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42036
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42038
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42039
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42041
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42044
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-44490
Files: package-lock.json, yarn.lock · reported by trivy
2 GHSA-7q8q-rj6j-mhjq
Files: package-lock.json, yarn.lock · reported by trivy
2 GHSA-9965-vmph-33xx
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-fvcv-3m26-pcqx
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-jqh4-m9w3-8hp9
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-m7pr-hjqh-92cm
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-pmv8-rq9r-6j72
Files: package-lock.json, yarn.lock · reported by trivy
2 GHSA-w9j2-pvgh-6h63
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
1 AAK-TASKS-003
Files: apps/mcp-server/src/server/tools/task-toolts.ts · reported by agent-audit-kit
1 CVE-2025-64718
Files: yarn.lock · reported by trivy
1 CVE-2026-33672
Files: yarn.lock · reported by trivy
1 CVE-2026-53550
Files: yarn.lock · reported by trivy
367 The model's answer could not be read.
Rules: GHSA-mp2f-45pm-3cg9, GHSA-3qcw-2rhx-2726, GHSA-7r86-cg39-jmmj and 119 more · Files: /repo/apps/mcp-server/yarn.lock, /repo/package-lock.json, /repo/yarn.lock and 6 more · reported by osv-scanner, trivy, agent-audit-kit
18 The review budget for this scan was already spent before these findings were reached.
Rules: GHSA-xhjh-pmcv-23jw, CVE-2026-42040, AAK-SUPPLY-005 and 4 more · Files: /repo/package-lock.json, /repo/yarn.lock, package-lock.json and 9 more · reported by osv-scanner, trivy, agent-audit-kit and 1 more
Critical vulnerabilities found in installed dependencies
The artifact contains critical vulnerabilities in its installed code dependencies, specifically GHSA-mp2f-45pm-3cg9 and GHSA-3qcw-2rhx-2726, located in `yarn.lock` and `package-lock.json` files. Additionally, numerous high-severity vulnerabilities are present across various dependencies, primarily within `yarn.lock` files. These findings indicate potential risks that warrant immediate 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 25; the rest are in the per-scanner reports above.