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.
14 critical findings reported by cisco-skill-scanner, 4 of them in the installed artifact. 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 -- nerlo-ingest-2o9x9aiv
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
45 findings · 6.2s
v0.3.74
3 findings · 1.2s
v0.2.0
0 findings · 3.1s
v0.2.0
0 findings · 3.1s
v0.71.0
22 findings · 0.2s
v2.3.8
47 findings · 6.4s
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.0s
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
7 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 11, 2026 | Flagged39 | — | 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 |
| Jul 30, 2026 | Flagged29 | — | cisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicable | completed |
| Jul 21, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: complete | rejected |
| Jul 20, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: complete | rejected |
| Jul 20, 2026 | Scan Halted | Clean → Flagged | agentshield: completecisco-skill-scanner: completeagent-audit-kit: complete | rejected |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·n/a: not applicable | completed |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·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 117 findings across every scanner that examined this package. 10 of 14 findings rated critical by their scanner were among the dismissals.
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.
12 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: COMMAND_INJECTION_JS_CHILD_PROCESS, DATA_EXFIL_JS_FS_ACCESS · Files: /repo/packages/create-mcp-ts/src/index.test.ts · reported by cisco-skill-scanner
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
17 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/packages/create-mcp-ts/src/index.ts, /repo/packages/mcp-scripts/src/eject.js, /repo/scripts/updateTemplatesDeps.cjs · reported by cisco-skill-scanner
4 COMMAND_INJECTION_JS_CHILD_PROCESS
Files: /repo/packages/create-mcp-ts/src/utils.ts, /repo/packages/mcp-scripts/src/index.ts · reported by cisco-skill-scanner
4 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
4 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
4 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json · reported by osv-scanner
4 LOW_ANALYZABILITY
Files: /repo/packages/mcp-scripts, /repo/packages/create-mcp-ts, /repo and 1 more · reported by cisco-skill-scanner
4 MANIFEST_MISSING_LICENSE
Critical command injection vulnerabilities found
The artifact contains critical command injection vulnerabilities in `utils.ts` and `index.ts` within the `create-mcp-ts` and `mcp-scripts` packages. These findings indicate a capability for shell execution. Additionally, numerous high severity vulnerabilities from `osv-scanner` and `trivy` are present in dependencies, which could introduce further risks.
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.
4 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/packages/create-mcp-ts/SKILL.md, /repo/packages/mcp-scripts/SKILL.md and 1 more · reported by cisco-skill-scanner
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-5j98-mcp5-4vw2
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-018
Files: packages/mcp-ts-template-default/src/index.ts · 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-5889
Files: package-lock.json · reported by trivy
1 CVE-2025-64756
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-12590
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-2391
Files: package-lock.json · reported by trivy
1 CVE-2026-26996
Files: package-lock.json · reported by trivy
1 CVE-2026-27606
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-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-4923
Files: package-lock.json · reported by trivy
1 CVE-2026-4926
Files: package-lock.json · reported by trivy
1 CVE-2026-69152
Files: package-lock.json · reported by trivy
1 CVE-2026-82417
Files: package-lock.json · reported by trivy
1 CVE-2026-8723
Files: package-lock.json · reported by trivy
1 GHSA-27v5-c462-wpq7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2883-xcg3-v3hh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4mjr-xmp4-gh2g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4x5r-pxfx-6jf8
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-5p4m-2wfm-xmqj
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-73wf-gq98-2v4g
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-c83g-rgw3-j3cx
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-j3q9-mxjg-w52f
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-q8mj-m7cp-5q26
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-w48q-cv73-mx4w
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-wqch-xfxh-vrr4
Files: /repo/package-lock.json · reported by osv-scanner
Showing 25 of 47; the rest are in the per-scanner reports above.