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.
2 critical findings reported by cisco-skill-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 -- remote-mcp-server-ft-poc
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.4s
v2.0.11
12 findings · 6.4s
v0.3.74
8 findings · 2.1s
v0.1.0
0 findings · 2.8s
v0.1.0
0 findings · 2.8s
v0.71.0
61 findings · 0.3s
v2.3.8
92 findings · 7.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.7s
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 | Flagged37 | — | 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 173 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 41 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 AAK-OAUTH-007
Files: src/app.ts, src/index.ts · reported by agent-audit-kit
2 GHSA-26pp-8wgv-hjvm
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-gq3j-xvxp-8hrf
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-q7jf-gf43-6x6p
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-v8w9-8mx6-g223
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-w5cr-2qhr-jqc5
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-MCP-018
Files: src/index.ts · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2025-13466
Files: package-lock.json · reported by trivy
1 CVE-2025-15284
Files: package-lock.json · reported by trivy
1 CVE-2025-48985
Files: package-lock.json · reported by trivy
1 CVE-2025-58362
Files: package-lock.json · reported by trivy
1 CVE-2025-59139
Files: package-lock.json · reported by trivy
1 CVE-2025-66414
Files: package-lock.json · reported by trivy
1 CVE-2025-69873
Files: package-lock.json · reported by trivy
1 CVE-2025-9910
Files: package-lock.json · reported by trivy
1 CVE-2026-0621
Files: package-lock.json · reported by trivy
1 CVE-2026-12590
Files: package-lock.json · reported by trivy
1 CVE-2026-1664
Files: package-lock.json · reported by trivy
1 CVE-2026-1721
Files: package-lock.json · reported by trivy
1 CVE-2026-2391
Files: package-lock.json · reported by trivy
1 CVE-2026-24398
Files: package-lock.json · reported by trivy
1 CVE-2026-24472
Files: package-lock.json · reported by trivy
1 CVE-2026-24473
Files: package-lock.json · reported by trivy
1 CVE-2026-24771
Files: package-lock.json · reported by trivy
1 CVE-2026-25536
Files: package-lock.json · reported by trivy
1 CVE-2026-29045
Files: package-lock.json · reported by trivy
1 CVE-2026-29085
Files: package-lock.json · reported by trivy
1 CVE-2026-29086
Files: package-lock.json · reported by trivy
1 CVE-2026-39407
Files: package-lock.json · reported by trivy
1 CVE-2026-39408
Files: package-lock.json · reported by trivy
1 CVE-2026-39409
Files: package-lock.json · reported by trivy
1 CVE-2026-39410
Files: package-lock.json · reported by trivy
1 CVE-2026-44455
Files: package-lock.json · reported by trivy
1 CVE-2026-44456
Files: package-lock.json · reported by trivy
1 CVE-2026-44457
Files: package-lock.json · reported by trivy
1 CVE-2026-44458
Files: package-lock.json · reported by trivy
1 CVE-2026-44459
Files: package-lock.json · reported by trivy
1 CVE-2026-47673
Files: package-lock.json · reported by trivy
1 CVE-2026-47674
Files: package-lock.json · reported by trivy
1 CVE-2026-47675
Files: package-lock.json · reported by trivy
1 CVE-2026-47676
Files: package-lock.json · reported by trivy
1 CVE-2026-4923
Files: package-lock.json · reported by trivy
1 CVE-2026-54286
Files: package-lock.json · reported by trivy
1 CVE-2026-54287
Files: package-lock.json · reported by trivy
1 CVE-2026-54288
Files: package-lock.json · reported by trivy
1 CVE-2026-54289
Files: package-lock.json · reported by trivy
1 CVE-2026-54290
Files: package-lock.json · reported by trivy
1 CVE-2026-56761
Files: package-lock.json · reported by trivy
1 CVE-2026-59895
Files: package-lock.json · reported by trivy
1 CVE-2026-59897
Files: package-lock.json · reported by trivy
1 CVE-2026-69207
Files: package-lock.json · reported by trivy
1 CVE-2026-71849
Files: package-lock.json · reported by trivy
1 CVE-2026-71850
Files: package-lock.json · reported by trivy
1 CVE-2026-8723
Files: package-lock.json · reported by trivy
1 CVE-2026-8769
Files: package-lock.json · reported by trivy
1 GHSA-27v5-c462-wpq7
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-2gcr-mfcq-wcc3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2mjp-6q6p-2qxm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-33vc-wfww-vjfv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-35p6-xmwp-9g52
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-38c4-r59v-3vqw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3hrh-pfw6-9m5x
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3vhc-576x-3qv4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-458j-xx4x-4375
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4992-7rv2-5pvq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4cwx-7wf7-3272
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-5pq2-9x2x-5p6w
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-69xw-7hcm-h432
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6v5v-wf23-fmfq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6wqw-2p9w-4vw4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-79qm-7rj5-m7r9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-866g-f22w-33x8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8j4g-w8fx-2239
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8r9q-7v3j-jr4g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8xcm-r25x-g524
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-92vj-g62v-jqhh
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-9r54-q6cx-xmh5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9vqf-7f2p-gf9v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-cvhv-6xm6-c3v4
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-f23p-vx2j-j53r
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f269-vfmq-vjvj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f577-qrjj-4474
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f67f-6cw9-8mq4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g8m3-5g58-fq7m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g9mf-h72j-4rw9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hm8q-7f3q-5f36
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j6c9-x7qj-28xf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jr45-8vmc-qm54
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m732-5p4w-x69g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m8rv-5g2x-5cg5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p6xx-57qc-3wxr
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p77w-8qqv-26rm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p88m-4jfj-68fv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pr7r-676h-xcf6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qp7p-654g-cw7p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qpx9-hpmf-5gmw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r354-f388-2fhh
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-r5rp-j6wh-rvv4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r7x9-8ph7-w8cg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rv63-4mwf-qqc2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rwvc-j5jr-mgvh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v3r7-h72x-cjcm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v9p9-hfj2-hcw8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w332-q679-j88p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w62v-xxxg-mg59
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wgpf-jwqj-8h8p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wmmm-f939-6g9c
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wqch-xfxh-vrr4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wwfh-h76j-fc44
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xf4j-xp2r-rqqx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xgm2-5f3f-mvvc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xpcf-pg52-r92g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xrhx-7g5j-rcj5
Files: /repo/package-lock.json · reported by osv-scanner
30 The review call did not complete.
Rules: COMMAND_INJECTION_EVAL, CVE-2026-67214, GHSA-2v37-7h3g-55p8 and 22 more · Files: /repo/worker-configuration.d.ts, package-lock.json, /repo/package-lock.json and 1 more · reported by cisco-skill-scanner, trivy, osv-scanner and 1 more
10 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, DATA_EXFIL_JS_NETWORK, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: SECURITY.md, /repo/src/utils.ts, /repo/worker-configuration.d.ts and 2 more · reported by agent-audit-kit, cisco-skill-scanner
1 The review budget for this scan was already spent before these findings were reached.
Rules: LOW_ANALYZABILITY · Files: /repo · reported by cisco-skill-scanner
Critical command injection and high-severity vulnerabilities.
The artifact includes critical command injection vulnerabilities in `worker-configuration.d.ts`, which could enable arbitrary shell execution. Additionally, numerous high-severity vulnerabilities are present in dependencies listed in `package-lock.json`, potentially leading to further system compromise. A high-severity DNS rebinding risk is also identified in `package.json`.
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 46; the rest are in the per-scanner reports above.