chromatic@18.13.6
Automate visual testing across browsers. Gather UI feedback. Versioned documentation.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package's import entry is a simple browser marker check, and its CLI network and upload activity is consistent with publishing visual test results. The manifest has no install lifecycle scripts or other evidence of automatic install-time behavior.
Decision evidence
public snapshot- The manifest describes Chromatic as a visual testing tool and defines its browser helper and CLI entry points.
- The root JavaScript entry only checks the browser user agent and URL for Chromatic markers.
- The CLI configures its GraphQL client to use the CHROMATIC_INDEX_URL endpoint and includes the session ID and CLI version.
- The CLI uploads build files to a formAction supplied by its API flow, consistent with publishing visual test results.
- The package manifest has no lifecycle scripts, so installation does not automatically run package code.
- The ordinary package import is a browser marker check; the upload behavior is in the CLI flow.
- Network and file-upload behavior is consistent with the package's stated visual testing purpose.
Source & flagged code
7 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-BUm1ZgBQ.cjsView on unpkg · L438Findings
Affected versions and remediation
This report applies to chromatic@18.13.6.
See all versions of chromatic for other recorded verdicts.
- Review the evidence and your use of chromatic@18.13.6 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.