Loading the registry…
An xmcp application with tool syntax
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 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 -- satori-mcp-server
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.7s
v2.0.11
5 findings · 8.0s
v0.3.74
3 findings · 1.7s
v0.1.0
0 findings · 3.3s
v0.1.0
0 findings · 3.3s
v0.71.0
71 findings · 0.4s
v2.3.8
120 findings · 9.1s
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.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 19, 2026 | Flagged48 | — | 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 199 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 23 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 CVE-2025-15284
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2025-69873
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-12590
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-2391
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-26996
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-27903
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-27904
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-8723
Files: pnpm-lock.yaml · reported by trivy
2 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2g4f-4pwh-qvx6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5c6j-r48x-rmvq
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-6rw7-vpxm-498p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7rx3-28cr-v5wh
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-q8mj-m7cp-5q26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v422-hmwv-36x6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: pnpm-lock.yaml · reported by agent-audit-kit
1 CVE-2025-13465
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-13466
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-58444
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-64756
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-2026-0621
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-12151
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13149
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13311
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13676
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-14257
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-15157
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-1525
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-1526
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-1527
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16221
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16728
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16729
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-18446
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-22036
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2229
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-25536
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-25547
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2950
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33532
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33671
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33672
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33750
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33916
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33937
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33938
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33939
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33940
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33941
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-34043
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45736
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4800
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4867
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-6321
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-6322
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69152
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-9277
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-9679
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-27v5-c462-wpq7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2mjp-6q6p-2qxm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2qvq-rjwj-gvw9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2w6w-674q-4c4q
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-37ch-88jc-xwx2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-395f-4hp3-45gv
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-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3mfm-83xf-c92r
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-42h9-826w-cgv3
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-43p4-m455-4f4j
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-48c2-rrv3-qjmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4992-7rv2-5pvq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4c8g-83qw-93j6
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-4w7w-66w2-5vf9
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-5j98-mcp5-4vw2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5xrq-8626-4rwp
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-6g55-p6wh-862q
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-7h2j-956f-4vf2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7p8r-x3mc-p8w7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7q8q-rj6j-mhjq
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-8xcm-r25x-g524
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-93m4-6634-74q7
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-9cx6-37pm-9jff
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f23m-r3pf-42rh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f886-m6hf-6m8v
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-fx2h-pf6j-xcff
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g9hg-qhmf-q45m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g9mf-h72j-4rw9
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-jqh4-m9w3-8hp9
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-m8rv-5g2x-5cg5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mmx7-hfxf-jppx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p88m-4jfj-68fv
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-p9ff-h696-f583
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-pmv8-rq9r-6j72
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-q3j6-qgpj-74h6
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-qj8w-gfj5-8c6v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r4q5-vmmm-2653
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r5fr-rjxr-66jc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2hh-gcrm-f6hx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2wj-q39q-566r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v39h-62p7-jpjc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v3r7-h72x-cjcm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v9p9-hfj2-hcw8
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-vrm6-8vpv-qv8q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vxpw-j846-p89q
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-w7jw-789q-3m8p
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-xhpv-hc6g-r9c6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xjpj-3mr7-gcpf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xx6v-rp6x-q39c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
23 The review budget for this scan was already spent before these findings were reached.
Rules: GHSA-w7fw-mjwx-w883, AAK-SEC-MD-001, GHSA-g8m3-5g58-fq7m and 17 more · Files: /repo/pnpm-lock.yaml, SECURITY.md, pnpm-lock.yaml and 3 more · reported by osv-scanner, agent-audit-kit, trivy and 1 more
Critical and high-severity vulnerabilities detected in dependencies.
The artifact contains dependencies with multiple critical and high-severity vulnerabilities, identified in `pnpm-lock.yaml`. Critical findings include CVE-2026-9277 and GHSA-5xrq-8626-4rwp. Numerous other high-severity vulnerabilities are also present in the dependency tree, requiring 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.