chromatic@18.13.4
Automate visual testing across browsers. Gather UI feedback. Versioned documentation.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends runtime telemetry automatically after a Storybook build failure, including a user-configurable command that may contain project-specific details. The opt-out reduces the risk, but the source does not establish in-run consent or disclosure, so this warrants a warning rather than a block.
Decision evidence
public snapshot- After a Storybook build failure, the CLI records the error category, stack trace, configurable build command and runtime details in a telemetry event.
- The event is sent through a GraphQL mutation named TrackCLITelemetryEvent.
- The GraphQL client targets CHROMATIC_INDEX_URL/graphql, a configurable Chromatic endpoint.
- Analytics can be disabled with CHROMATIC_DISABLE_ANALYTICS, CHROMATIC_DISABLE_TELEMETRY or DO_NOT_TRACK.
- buildCommand is a CLI option, so the telemetry field can contain a user-configured command.
- The package has no install lifecycle scripts, and its root entry only checks whether a browser is running Chromatic.
- The telemetry is limited to CLI build failures; the stack trace is scrubbed, and the Git email is hashed.
- An environment-variable opt-out is provided.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/execa-D4ZUVBkd.cjsView on unpkg · L2Package source references dynamic require/import behavior.
dist/node.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to chromatic@18.13.4.
See all versions of chromatic for other recorded verdicts.
- Review the evidence and your use of chromatic@18.13.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.