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.
8 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 -- mcp-server-reference
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
13 findings · 9.9s
v0.3.74
5 findings · 3.2s
v0.1.0
0 findings · 3.0s
v0.1.0
0 findings · 3.0s
v0.71.0
137 findings · 0.6s
v2.3.8
185 findings · 8.6s
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 19, 2026 | Flagged39 | — | 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 340 findings across every scanner that examined this package. None of the 8 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 86 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-23c5-xmqv-rm74
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3jxr-9vmj-r5cp
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3ppc-4f35-3m26
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3v7f-55p6-f55p
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-7r86-cg39-jmmj
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-8h8q-6873-q5fj
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml, /repo/basic/pnpm-lock.yaml and 1 more · reported by trivy, osv-scanner
4 GHSA-c2c7-rcm5-vvqj
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-f886-m6hf-6m8v
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-f88m-g3jw-g9cj
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml, basic/pnpm-lock.yaml and 1 more · reported by osv-scanner, trivy
4 GHSA-h25m-26qc-wcjf
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml, basic/pnpm-lock.yaml and 1 more · reported by osv-scanner, trivy
4 GHSA-mh99-v99m-4gvg
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-q4gf-8mx6-v5v3
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml, /repo/basic/pnpm-lock.yaml and 1 more · reported by trivy, osv-scanner
4 GHSA-rgw5-rvv9-x895
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-w2fm-25vw-vh7f
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml, /repo/basic/pnpm-lock.yaml and 1 more · reported by trivy, osv-scanner
3 AAK-LEGAL-002
Files: package.json, with-authorization/package.json, basic/package.json · reported by agent-audit-kit
3 CVE-2026-41305
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
3 CVE-2026-45623
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
3 CVE-2026-69153
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
3 CVE-2026-73646
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
3 GHSA-6g55-p6wh-862q
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-fxqj-rqcc-2cmp
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-qx2v-qp2m-jg93
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-r28c-9q8g-f849
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 CVE-2025-13466
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2025-15284
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2025-59471
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2025-66414
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2025-69873
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-0621
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-25536
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-27980
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-29057
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44288
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-44573
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44574
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44575
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44576
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44578
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44579
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44580
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44581
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-45109
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-4923
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-4926
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-64641
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-64643
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-64645
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-64646
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-64648
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-64649
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-67213
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-67214
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 CVE-2026-8723
Files: basic/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by trivy
2 GHSA-25h7-pfq9-p65f
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-267c-6grr-h53f
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-26hh-7cqf-hhc6
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-27v5-c462-wpq7
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-28wg-ghj8-5hjv
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2g4f-4pwh-qvx6
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2v37-7h3g-55p8
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-345p-7cg4-v4c7
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-36qx-fr4f-26g5
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3x4c-7xq6-9pq8
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4633-3j49-mh5q
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-492v-c6pp-mqqv
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4c39-4ccg-62r3
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-68g3-v927-f742
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6rw7-vpxm-498p
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-86j7-9j95-vpqj
Files: /repo/with-authorization/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-89xv-2m56-2m9x
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8r9q-7v3j-jr4g
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-955p-x3mx-jcvp
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-9g9p-9gw9-jx7f
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c4j6-fc7j-m34r
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-ffhc-5mcf-pf4q
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-ggv3-7p47-pfv8
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h64f-5h5j-jqjh
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-j3q9-mxjg-w52f
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-m99w-x7hq-7vfj
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mg66-mrh9-m8jx
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh29-5h37-fv8m
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-p9j2-gv94-2wf4
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rf6f-7fwh-wjgh
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w48q-cv73-mx4w
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-wfc6-r584-vfw7
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-wqch-xfxh-vrr4
Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-xg6x-h9c9-2m83
Files: with-authorization/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml · reported by trivy, osv-scanner
2 HIDDEN_EXECUTABLE_SCRIPT
Files: /repo/with-authorization/src/app/.well-known/oauth-authorization-server/route.ts, /repo/with-authorization/src/app/.well-known/oauth-protected-resource/route.ts · reported by cisco-skill-scanner
1 CVE-2026-23745
Files: with-authorization/pnpm-lock.yaml · reported by trivy
1 CVE-2026-23950
Files: with-authorization/pnpm-lock.yaml · reported by trivy
1 CVE-2026-24842
Files: with-authorization/pnpm-lock.yaml · reported by trivy
1 CVE-2026-31802
Files: with-authorization/pnpm-lock.yaml · reported by trivy
1 CVE-2026-33468
Files: with-authorization/pnpm-lock.yaml · reported by trivy
1 CVE-2026-35209
Files: with-authorization/pnpm-lock.yaml · reported by trivy
1 CVE-2026-41242
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44289
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44290
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44291
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44293
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48068
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48069
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48712
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53512
Files: with-authorization/pnpm-lock.yaml · reported by trivy
1 CVE-2026-53518
Files: with-authorization/pnpm-lock.yaml · reported by trivy
1 CVE-2026-59873
Files: with-authorization/pnpm-lock.yaml · reported by trivy
1 CVE-2026-59874
Files: with-authorization/pnpm-lock.yaml · reported by trivy
1 GHSA-23hp-3jrh-7fpw
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-34x7-hfp2-rc4v
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5375-pq7m-f5r2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-66ff-xgx4-vchm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-737v-mqg7-c878
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8cpq-38p9-67gx
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8qq5-rm4j-mr97
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8x88-c5mf-7j5w
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-99h5-pjcv-gr6v
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9ppj-qmqm-q256
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fmh4-wcc4-5jm3
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jvwf-75h9-cwgg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-pv5w-4p9q-p3v2
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-pw9m-5jxm-xr6h
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qq9h-g4jm-xgf3
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r6q2-hw4h-h46w
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wcpc-wj8m-hjx6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wmrf-hv6w-mr66
Files: /repo/with-authorization/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xq3m-2v4x-88gg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
61 The review budget for this scan was already spent before these findings were reached.
Rules: GHSA-q8mj-m7cp-5q26, CVE-2026-44577, GHSA-h67p-54hq-rp68 and 34 more · Files: /repo/basic/pnpm-lock.yaml, /repo/with-authorization/pnpm-lock.yaml, basic/pnpm-lock.yaml and 9 more · reported by osv-scanner, trivy, cisco-skill-scanner
25 The review call did not complete.
Rules: GHSA-x732-6j76-qmhm, GHSA-83g3-92jg-28cx, GHSA-qq9h-g4jm-xgf3 and 19 more · Files: /repo/with-authorization/pnpm-lock.yaml, with-authorization/pnpm-lock.yaml, basic/public/search-index.json and 3 more · reported by osv-scanner, trivy, agent-audit-kit and 1 more
Critical vulnerabilities and hidden executable scripts identified.
This artifact includes critical vulnerabilities in its pnpm-lock.yaml files, which could enable remote code execution or data compromise through dependency exploitation. Hidden executable scripts are also present in route.ts files, indicating a capability for shell execution. These findings, along with numerous other high severity vulnerabilities, require thorough review.
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.