chromatic@18.6.0
Automate visual testing across browsers. Gather UI feedback. Versioned documentation.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiDirect inspection found no lifecycle hook, self-dependency, hidden payload loader, or concrete malicious execution chain. Static findings are explained by bundled CLI and third-party code.
Decision evidence
public snapshot- The manifest exposes library and explicit CLI entrypoints, with no lifecycle-script section.
- The three flagged bundles start with generated Sentry debug-ID scaffolding; their dynamic-code findings are consistent with bundled third-party tooling rather than an install-time payload.
- The manifest has no runtime dependency on chromatic itself.
- The CLI reads project files and environment configuration and contacts Chromatic service endpoints when explicitly run.
Source & flagged code
11 flaggedSource contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/v1-BPL0QeOt.cjsView on unpkg · L30A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/v1-BPL0QeOt.cjsView on unpkg · L60Findings
Affected versions and remediation
This report applies to chromatic@18.6.0.
See all versions of chromatic for other recorded verdicts.
- Review the evidence and your use of chromatic@18.6.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.