Found by crawling (provenance, not a security rating)
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.
29 critical findings reported by cisco-skill-scanner, 10 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Install
Choose your runtime: the CLI writes the mcpServers config entry for that target.
Your view:Composite recomputed: 7 of 7 scanners in your view
5 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.
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.
Upheld as real
8
Dismissed as false positives
0
Not reviewed
282
Out of 290 findings across every scanner that examined this package. None of the 29 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 282 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Upheld — the review declined to dismiss these
The model could have called any of these a false positive and did not.
8LOW_ANALYZABILITY
Files: /repo, /repo/packages/mcp-tools, /repo/shared and 5 more · reported by cisco-skill-scanner
Not reviewed
282The review call did not complete.
Rules: COMMAND_INJECTION_EVAL, COMMAND_INJECTION_JS_FUNCTION_CONSTRUCTOR, YARA_credential_harvesting_generic and 16 more · Files: /repo/backend/src/execute-cesium-code.integration.test.ts, /repo/packages/codegen-cesium/src/pipeline/ast-verifier.test.ts, /repo/packages/codegen-cesium/src/pipeline/generate-verified-cesium-code.test.ts and 79 more · reported by cisco-skill-scanner, nerlo-behavioral, agent-audit-kit
What the review concluded
Critical command injection risks in core code.
The artifact contains critical command injection vulnerabilities in `/repo/packages/codegen-cesium/src/pipeline/ast-verifier.ts`. These findings indicate potential for shell execution via `eval` and `Function` constructor. Such capabilities could allow arbitrary code execution within the artifact's environment.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
What to look at
COMMAND_INJECTION_EVAL · /repo/backend/src/execute-cesium-code.integration.test.ts · critical · reported by cisco-skill-scanner
COMMAND_INJECTION_EVAL · /repo/backend/src/execute-cesium-code.integration.test.ts · critical · reported by cisco-skill-scanner
COMMAND_INJECTION_EVAL · /repo/backend/src/execute-cesium-code.integration.test.ts · critical · reported by cisco-skill-scanner
COMMAND_INJECTION_EVAL · /repo/backend/src/execute-cesium-code.integration.test.ts · critical · reported by cisco-skill-scanner
COMMAND_INJECTION_EVAL · /repo/packages/codegen-cesium/src/pipeline/ast-verifier.test.ts · critical · reported by cisco-skill-scanner
COMMAND_INJECTION_EVAL · /repo/packages/codegen-cesium/src/pipeline/ast-verifier.test.ts · critical · reported by cisco-skill-scanner
· · critical · reported by cisco-skill-scanner
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.