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.
1 critical finding 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 -- nips-on-nostr
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.
v1.4.0
2 findings · 0.5s
v0.3.74
8 findings · 3.4s
v0.1.0
1 finding · 3.8s
v0.1.0
0 findings · 3.8s
v0.71.0
28 findings · 0.3s
v2.3.8
56 findings · 6.7s
v2.0.11
No skill bundle was found in this artifact. What each scanner covers
0 findings · 6.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 · 1.8s
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: completecisco-skill-scanner ·n/a: not applicableagent-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 95 findings across every scanner that examined this package. None of the 1 finding 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.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
2 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: permissions-no-block, hooks-no-pretooluse · Files: .vscode/settings.json · reported by agentshield
The model could have called any of these a false positive and did not.
2 AAK-SUPPLY-001
Files: .mcp.json · reported by agent-audit-kit
2 CVE-2026-40181
Files: package-lock.json · reported by trivy
2 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-2j2x-hqr9-3h42
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
2
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-MCP-005, AAK-MCP-007 · Files: .mcp.json · reported by agent-audit-kit
Critical dependency vulnerability and potential credential exposure.
The artifact includes a critical vulnerability in a dependency listed in `package-lock.json`, which could enable remote code execution or data exposure. Numerous other high-severity dependency vulnerabilities are also present. A supply chain finding in `.mcp.json` indicates potential risks in dependency management, and a finding in `AppProvider.ts` suggests possible credential access or sensitive data leakage.
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.
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-v6h2-p8h4-qcjw
Files: /repo/package-lock.json · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-MCP-ATTEST-001
Files: .mcp.json · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2025-13465
Files: package-lock.json · reported by trivy
1 CVE-2025-5889
Files: package-lock.json · reported by trivy
1 CVE-2025-64756
Files: package-lock.json · reported by trivy
1 CVE-2025-66400
Files: package-lock.json · reported by trivy
1 CVE-2025-68470
Files: package-lock.json · reported by trivy
1 CVE-2026-13149
Files: package-lock.json · reported by trivy
1 CVE-2026-14257
Files: package-lock.json · reported by trivy
1 CVE-2026-22029
Files: package-lock.json · reported by trivy
1 CVE-2026-26996
Files: package-lock.json · reported by trivy
1 CVE-2026-27903
Files: package-lock.json · reported by trivy
1 CVE-2026-27904
Files: package-lock.json · reported by trivy
1 CVE-2026-2950
Files: package-lock.json · reported by trivy
1 CVE-2026-33532
Files: package-lock.json · reported by trivy
1 CVE-2026-33671
Files: package-lock.json · reported by trivy
1 CVE-2026-33672
Files: package-lock.json · reported by trivy
1 CVE-2026-33750
Files: package-lock.json · reported by trivy
1 CVE-2026-41305
Files: package-lock.json · reported by trivy
1 CVE-2026-45623
Files: package-lock.json · reported by trivy
1 CVE-2026-4800
Files: package-lock.json · reported by trivy
1 CVE-2026-53666
Files: package-lock.json · reported by trivy
1 CVE-2026-53669
Files: package-lock.json · reported by trivy
1 CVE-2026-67213
Files: package-lock.json · reported by trivy
1 CVE-2026-67214
Files: package-lock.json · reported by trivy
1 CVE-2026-69152
Files: package-lock.json · reported by trivy
1 CVE-2026-69153
Files: package-lock.json · reported by trivy
1 CVE-2026-73646
Files: package-lock.json · reported by trivy
1 GHSA-25h7-pfq9-p65f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2w69-qvjg-hvjx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-337j-9hxr-rhxg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-48c2-rrv3-qjmp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4fh9-h7wg-q85m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-58qx-3vcg-4xpx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5j98-mcp5-4vw2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5p4m-2wfm-xmqj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5xrq-8626-4rwp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-93m4-6634-74q7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-96hv-2xvq-fx4p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9jcx-v3wj-wh4m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f23m-r3pf-42rh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g4jq-h2w9-997c
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-h67p-54hq-rp68
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jqfw-vq24-v9c3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mh29-5h37-fv8m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p9ff-h696-f583
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r5fr-rjxr-66jc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rf6f-7fwh-wjgh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wrjc-x8rr-h8h6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xffm-g5w8-qvg7
Files: /repo/package-lock.json · reported by osv-scanner
1 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/src/hooks/useOfficialNips.ts · reported by nerlo-behavioral
Showing 24 of 24; the rest are in the per-scanner reports above.