chromatic@18.9.3
Automate visual testing across browsers. Gather UI feedback. Versioned documentation.
AI Security Review
scanned 19d ago · by lpm-firewall-aiSource inspection found expected Chromatic CLI, configuration, and build upload behavior. The scanner’s Unicode concern maps to parser identifier tables; the inspected code did not establish malicious behavior.
Decision evidence
public snapshot- The manifest identifies Chromatic as a Storybook testing CLI and declares its runtime entrypoints; no lifecycle hook appears in the inspected manifest.
- The CLI dispatches to an explicitly selected command, including its interactive initialization task.
- The flagged Unicode characters occur in JavaScript identifier handling and parser tables, not in bidi control characters.
- The runtime reads Chromatic project configuration and uploads build files through the client-provided upload action.
- The Turbosnap bundle checks the Storybook directory and its dependent story files.
Source & flagged code
6 flaggedPackage source references dynamic require/import behavior.
dist/turbosnapManifest-nE5p1wOL.cjsView on unpkg · L2Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/projectFiles-CTjP5AZJ.cjsView on unpkg · L15Findings
Affected versions and remediation
This report applies to chromatic@18.9.3.
See all versions of chromatic for other recorded verdicts.
- Review the evidence and your use of chromatic@18.9.3 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.