chromatic@18.9.4
Automate visual testing across browsers. Gather UI feedback. Versioned documentation.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner findings are explained by bundled CLI dependencies and explicit visual-testing functionality. Source inspection found no lifecycle hook, hidden payload, or concrete malicious data flow.
Decision evidence
public snapshot- The manifest exposes command-line binaries but contains no lifecycle scripts, so installation does not trigger package code.
- The flagged Storybook helper only normalizes project paths and derives relative paths.
- The flagged v1 bundle contains TurboSnap dependency-tracing logic over Storybook and package-lock files.
- The runtime reads the Chromatic project token supplied by the caller for its authenticated CLI workflow.
- The noPackageJson bundle reports that the CLI must be run from a JavaScript project.
- Bundled dependencies contain dynamic loading, process execution, and network primitives, but inspection found no concealed payload or install-time activation.
- CHROMATIC_INDEX_URL is configurable, but the default is index.chromatic.com and the token is caller-supplied for Chromatic authentication.
Source & flagged code
9 flaggedPackage source references dynamic require/import behavior.
dist/node.cjsView on unpkg · L1Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/v1-CCLANSv5.cjsView on unpkg · L29Findings
Affected versions and remediation
This report applies to chromatic@18.9.4.
See all versions of chromatic for other recorded verdicts.
- Review the evidence and your use of chromatic@18.9.4 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.