Loading the registry…
Summarize your chat messages.
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.
2 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-chatsum
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 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
v0.3.74
4 findings · 0.8s
v0.71.0
27 findings · 0.3s
v2.3.8
27 findings · 7.5s
v2.0.11
No skill bundle was found in this artifact. What each scanner covers
0 findings · 6.6s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 2.9s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 2.9s
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.2s
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 | Flagged43 | — | agentshield: completecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-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 58 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
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.
2 GHSA-r292-9mhp-454m
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
1 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 CVE-2024-12905
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-48387
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-5889
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-59343
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-66414
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13149
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-14257
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23745
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23950
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-24842
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-26960
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-26996
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27903
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27904
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-29786
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-31802
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33750
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-3449
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42338
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53655
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59871
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59873
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59874
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59875
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69152
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69192
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-23hp-3jrh-7fpw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-34x7-hfp2-rc4v
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-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-83g3-92jg-28cx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8cj5-5rvv-wf4v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8qq5-rm4j-mr97
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8x88-c5mf-7j5w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9ppj-qmqm-q256
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-gvwx-54wh-qm9j
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-mwp4-54f8-5fhr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-pq67-2wwv-3xjx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qffp-2rhf-9h96
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r6q2-hw4h-h46w
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-v2v4-37r5-5v8g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v6h2-p8h4-qcjw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vj76-c3g6-qr5v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vmf3-w455-68vh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vpq2-c234-7xj6
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-w8wr-v893-vjvp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001 · Files: SECURITY.md · reported by agent-audit-kit
Critical vulnerabilities in dependencies
The artifact includes critical vulnerabilities in its dependencies, identified in `pnpm-lock.yaml`. It also contains components that could enable network egress via DNS rebinding, noted in `package.json`. Additionally, third-party OAuth integration is present, which may involve credential access.
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 39; the rest are in the per-scanner reports above.