canvasxpress-cli@68.3.0
Node program to run canvasXpress in the command line
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe suspicious signals arise from a bundled minified visualization library and the CLI's intended headless-browser rendering workflow. The package has no install-time execution or concrete malicious behavior.
Decision evidence
public snapshot- The flagged large source file identifies itself as the CanvasXpress 68.3 visualization library, consistent with generated/minified library code.
- Dynamic loading occurs only for the explicit canvas command and uses the path supplied by the CLI user.
- Browser navigation and in-page evaluation occur in the rendering command path, not during installation or import.
- The manifest defines a CLI and dependencies but no lifecycle scripts.
- No install, preinstall, postinstall, or prepare hook is declared.
- No credential or environment harvesting, secret exfiltration, persistence, or destructive action was found.
- Network access is part of user-requested rendering of local or supplied URL input.
- The eval matches are within the bundled visualization library's function/event reconstruction logic, not a hidden payload loader.
Source & flagged code
5 flaggedSource contains an obfuscated payload loader that reconstructs and executes hidden code.
src/canvasXpress.jsView on unpkg · L26Package source references a known benign dynamic code generation pattern.
src/canvasXpress.jsView on unpkg · L26The flagged large source file identifies itself as the CanvasXpress 68.3 visualization library, consistent with generated/minified library code.
Findings
Affected versions and remediation
This report applies to canvasxpress-cli@68.3.0.
See all versions of canvasxpress-cli for other recorded verdicts.
- Review the evidence and your use of canvasxpress-cli@68.3.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.