canvasxpress-cli@69.0.0
Node program to run canvasXpress in the command line
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package appears to be a user-invoked renderer with no install lifecycle hook, but the primary bundle's raw NUL bytes leave material source behavior unresolved. This prevents a source-grounded clean verdict.
Decision evidence
public snapshot- The primary browser bundle contains raw NUL bytes, preventing reliable complete static parsing of that file.
- Package metadata exposes a CanvasXpress CLI and declares Playwright as a dependency.
- The renderer launches Chromium only after a user invokes a rendering command.
- package.json has no preinstall, install, or postinstall lifecycle script.
- No credential collection, package-controlled endpoint, or confirmed exfiltration was established in the inspected CLI code.
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 · L26Findings
Affected versions and remediation
This report applies to canvasxpress-cli@69.0.0.
See all versions of canvasxpress-cli for other recorded verdicts.
- Review the evidence and your use of canvasxpress-cli@69.0.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.