chromatic@17.8.0
Automate visual testing across browsers. Gather UI feedback. Versioned documentation.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection found a normal Chromatic CLI package: no lifecycle hook, no import-time malicious behavior, and risky primitives are tied to explicit CLI build/upload workflows. Network telemetry/API use and child process execution are package-aligned and user-invoked.
Decision evidence
public snapshot- package.json has no lifecycle scripts; bin only maps chroma/chromatic/chromatic-cli to dist/bin.cjs
- isChromatic.js and isChromatic.mjs only inspect browser userAgent/location for Chromatic markers
- dist/bin.cjs dispatches explicit CLI subcommands and loads dotenv config; no install-time execution
- dist/node-src-NjW8_TQU.cjs network calls use Chromatic build/share APIs and user/project tokens for the CLI service
- child_process/execa use is for user-invoked Storybook/React Native build commands, not hidden execution
- scanner unicode hit is bundled parser/entity Unicode tables in dist/build-CjuKDeXS.cjs, not Trojan Source control flow
Source & flagged code
4 flaggedSource contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/build-CjuKDeXS.cjsView on unpkg · L4Package source references dynamic require/import behavior.
dist/build-CjuKDeXS.cjsView on unpkg · L2Findings
Affected versions and remediation
This report applies to chromatic@17.8.0.
See all versions of chromatic for other recorded verdicts.
- Review the evidence and your use of chromatic@17.8.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.