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.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 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.7s
v0.3.74
3 findings · 1.1s
v0.1.0
3 findings · 4.0s
v0.71.0
46 findings · 0.3s
v2.3.8
46 findings · 8.6s
v2.0.11
No skill bundle was found in this artifact. What each scanner covers
0 findings · 8.1s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 4.0s
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 · 2.6s
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 19, 2026 | Flagged44 | — | agentshield: completecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction ·n/a: not applicablecapslock ·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 98 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 1 finding 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.
3 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/src/services/wikipedia.service.ts · reported by nerlo-behavioral
2 GHSA-42h9-826w-cgv3
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-7q8q-rj6j-mhjq
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-jqh4-m9w3-8hp9
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-mmx7-hfxf-jppx
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-pmv8-rq9r-6j72
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-r4q5-vmmm-2653
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
1 AAK-ANTHROPIC-SDK-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 CVE-2025-13466
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-15284
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-58754
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-62718
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-65945
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-66414
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-69873
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-0621
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-12143
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-12590
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2391
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-25536
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-25639
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-40175
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41907
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42033
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42034
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42035
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42036
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42037
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42038
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42039
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42040
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42041
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42042
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42043
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42044
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42264
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44486
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44487
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44488
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44490
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44494
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44495
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44496
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45736
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48779
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4923
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4926
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-8723
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-27v5-c462-wpq7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-345p-7cg4-v4c7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-35jp-ww65-95wh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3g43-6gmg-66jw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3p68-rc4w-qgx5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3w6x-2g7m-8v23
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-43fc-jf86-j433
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-445q-vr5w-6q77
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4hjh-wcwx-xvwj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-58qx-3vcg-4xpx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5c9x-8gcm-mpgx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-62hf-57xw-28j9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6chq-wfr3-2hj9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-777c-7fjr-54vf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-869p-cjfg-cm3x
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-898c-q2cr-xwhg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8r9q-7v3j-jr4g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-96hv-2xvq-fx4p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fvcv-3m26-pcqx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hfxv-24rg-xrqf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hmw2-7cc7-3qxx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j5f8-grm9-p9fc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m7pr-hjqh-92cm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p92q-9vqr-4j8v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-pf86-5x62-jrwf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-pmwg-cvhr-8vh7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q8qp-cvcw-x6jj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vf2m-468p-8v99
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w48q-cv73-mx4w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w5hq-g745-h8pq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w7fw-mjwx-w883
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w9j2-pvgh-6h63
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wqch-xfxh-vrr4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xhjh-pmcv-23jw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xx6v-rp6x-q39c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 The model did not answer for these findings.
Rules: GHSA-v422-hmwv-36x6 · Files: /repo/pnpm-lock.yaml · reported by osv-scanner
Multiple high-severity vulnerabilities detected.
The artifact contains numerous high-severity vulnerabilities, primarily in its dependencies. Specific findings indicate potential for network egress via DNS rebind in `package.json` and credential access or data exfiltration through an Anthropic SDK in `src/index.ts`. Many other high-severity vulnerabilities are present across various dependencies listed in `pnpm-lock.yaml`.
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 25 of 25; the rest are in the per-scanner reports above.