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.
3 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 -- trade_mcp
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.5s
v2.0.11
56 findings · 7.2s
v0.3.74
6 findings · 2.1s
v0.1.0
0 findings · 2.8s
v0.1.0
0 findings · 2.8s
v0.71.0
100 findings · 0.2s
v2.3.8
124 findings · 6.7s
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.9s
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 | Flagged36 | — | 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 286 findings across every scanner that examined this package. None of the 3 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 108 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.
3 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
3 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
3 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json · reported by osv-scanner
3 UNANALYZABLE_BINARY
Files: /repo/Trade_MCP.pptx!/ppt/fonts/IBMPlexSansSemiBold-regular.fntdata, /repo/Trade_MCP.pptx!/ppt/fonts/SoraExtraLight-bold.fntdata, /repo/Trade_MCP.pptx!/ppt/fonts/SoraMedium-bold.fntdata · reported by cisco-skill-scanner
2 CVE-2026-13149
Files: package-lock.json · reported by trivy
2 CVE-2026-14257
Files: package-lock.json · reported by trivy
2 CVE-2026-26996
Files: package-lock.json · reported by trivy
2 CVE-2026-27903
Files: package-lock.json · reported by trivy
2 CVE-2026-27904
Files: package-lock.json · reported by trivy
2 CVE-2026-33750
Files: package-lock.json · reported by trivy
2 CVE-2026-48779
Files: package-lock.json · reported by trivy
2 CVE-2026-69152
Files: package-lock.json · reported by trivy
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-5c6j-r48x-rmvq
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-8h8q-6873-q5fj
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-96hv-2xvq-fx4p
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-f88m-g3jw-g9cj
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-h25m-26qc-wcjf
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-mmx7-hfxf-jppx
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-mwv6-3258-q52c
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-q4gf-8mx6-v5v3
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-r4q5-vmmm-2653
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
1 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-SPLUNK-TOKLOG-001
Files: scripts/zerodha.js · 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-27152
Files: package-lock.json · reported by trivy
1 CVE-2025-55173
Files: package-lock.json · reported by trivy
1 CVE-2025-55182
Files: package-lock.json · reported by trivy
1 CVE-2025-57752
Files: package-lock.json · reported by trivy
1 CVE-2025-57822
Files: package-lock.json · reported by trivy
1 CVE-2025-59471
Files: package-lock.json · reported by trivy
1 CVE-2025-62718
Files: package-lock.json · reported by trivy
1 CVE-2025-65945
Files: package-lock.json · reported by trivy
1 CVE-2025-66414
Files: package-lock.json · reported by trivy
1 CVE-2026-0621
Files: package-lock.json · reported by trivy
1 CVE-2026-25536
Files: package-lock.json · reported by trivy
1 CVE-2026-25639
Files: package-lock.json · reported by trivy
1 CVE-2026-27980
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-41305
Files: package-lock.json · reported by trivy
1 CVE-2026-41907
Files: package-lock.json · reported by trivy
1 CVE-2026-42033
Files: package-lock.json · reported by trivy
1 CVE-2026-42034
Files: package-lock.json · reported by trivy
1 CVE-2026-42035
Files: package-lock.json · reported by trivy
1 CVE-2026-42042
Files: package-lock.json · reported by trivy
1 CVE-2026-42043
Files: package-lock.json · reported by trivy
1 CVE-2026-44486
Files: package-lock.json · reported by trivy
1 CVE-2026-44487
Files: package-lock.json · reported by trivy
1 CVE-2026-44492
Files: package-lock.json · reported by trivy
1 CVE-2026-44495
Files: package-lock.json · reported by trivy
1 CVE-2026-44496
Files: package-lock.json · reported by trivy
1 CVE-2026-44573
Files: package-lock.json · reported by trivy
1 CVE-2026-44575
Files: package-lock.json · reported by trivy
1 CVE-2026-44578
Files: package-lock.json · reported by trivy
1 CVE-2026-44579
Files: package-lock.json · reported by trivy
1 CVE-2026-44580
Files: package-lock.json · reported by trivy
1 CVE-2026-44581
Files: package-lock.json · reported by trivy
1 CVE-2026-45109
Files: package-lock.json · reported by trivy
1 CVE-2026-45623
Files: package-lock.json · reported by trivy
1 CVE-2026-45736
Files: package-lock.json · reported by trivy
1 CVE-2026-4926
Files: package-lock.json · reported by trivy
1 CVE-2026-59869
Files: package-lock.json · reported by trivy
1 CVE-2026-64641
Files: package-lock.json · reported by trivy
1 CVE-2026-64643
Files: package-lock.json · reported by trivy
1 CVE-2026-64645
Files: package-lock.json · reported by trivy
1 CVE-2026-64646
Files: package-lock.json · reported by trivy
1 CVE-2026-64648
Files: package-lock.json · reported by trivy
1 CVE-2026-64649
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-73646
Files: package-lock.json · reported by trivy
1 CVE-2026-8723
Files: package-lock.json · reported by trivy
1 GHSA-23hp-3jrh-7fpw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-25h7-pfq9-p65f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-267c-6grr-h53f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-26hh-7cqf-hhc6
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-2v37-7h3g-55p8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-345p-7cg4-v4c7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-34x7-hfp2-rc4v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-36qx-fr4f-26g5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3g43-6gmg-66jw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3p68-rc4w-qgx5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3x4c-7xq6-9pq8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-43fc-jf86-j433
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-5c9x-8gcm-mpgx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-62hf-57xw-28j9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-68g3-v927-f742
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6chq-wfr3-2hj9
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-7q8q-rj6j-mhjq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-83g3-92jg-28cx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-869p-cjfg-cm3x
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-898c-q2cr-xwhg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-89xv-2m56-2m9x
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8qq5-rm4j-mr97
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-8x88-c5mf-7j5w
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9g9p-9gw9-jx7f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9ppj-qmqm-q256
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9qr9-h5gf-34mp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-c4j6-fc7j-m34r
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-ffhc-5mcf-pf4q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g5qg-72qw-gw5v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-ggv3-7p47-pfv8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hfxv-24rg-xrqf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j5f8-grm9-p9fc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jr5f-v2jv-69x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m99w-x7hq-7vfj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mg66-mrh9-m8jx
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-p92q-9vqr-4j8v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p9j2-gv94-2wf4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pf86-5x62-jrwf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pjwm-pj3p-43mv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pmwg-cvhr-8vh7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qffp-2rhf-9h96
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qj8w-gfj5-8c6v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r292-9mhp-454m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r6q2-hw4h-h46w
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-w48q-cv73-mx4w
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w5hq-g745-h8pq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w8wr-v893-vjvp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xv57-4mr9-wg8v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xx6v-rp6x-q39c
Files: /repo/package-lock.json · reported by osv-scanner
1 YARA_prompt_injection_unicode_steganography
Files: /repo/Trade_MCP.pptx · reported by cisco-skill-scanner
101 The review budget for this scan was already spent before these findings were reached.
Rules: UNANALYZABLE_BINARY, CVE-2025-64718, GHSA-wfc6-r584-vfw7 and 62 more · Files: /repo/Trade_MCP.pptx!/ppt/fonts/IBMPlexSans-bold.fntdata, package-lock.json, /repo/package-lock.json and 28 more · reported by cisco-skill-scanner, trivy, osv-scanner and 1 more
7 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: UNANALYZABLE_BINARY, FILE_MAGIC_MISMATCH, ARCHIVE_FILE_DETECTED · Files: /repo/Trade_MCP.pptx!/ppt/fonts/Sora-regular.fntdata, /repo/Trade_MCP.pptx, /repo/Trade_MCP.pptx!/ppt/fonts/IBMPlexSansMedium-boldItalic.fntdata and 3 more · reported by cisco-skill-scanner
Critical vulnerabilities, DNS rebinding, and credential logging.
This artifact has critical vulnerabilities in its dependencies, identified in `package-lock.json`. It also presents a potential for DNS rebinding via `package.json`. Additionally, Splunk tokens are logged in `scripts/zerodha.js`, risking 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 25; the rest are in the per-scanner reports above.