chromatic@18.7.0
Automate visual testing across browsers. Gather UI feedback. Versioned documentation.
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed runtime behavior fits Chromatic’s CLI and browser detection functions. Scanner indicators alone do not establish malicious behavior.
Decision evidence
public snapshot- The manifest maps the package entrypoints to the browser detector and Node CLI; it defines no lifecycle script.
- The CLI exposes an analytics opt-out through environment settings.
- The runtime sends GraphQL requests through its configured client.
- The flagged bundles import CLI, filesystem, and project-discovery modules consistent with the package’s visual testing purpose.
- Scanner labels for dynamic loading, network access, environment access, and invisible Unicode do not establish an attack; inspected source shows CLI and product behavior.
Source & flagged code
10 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/node-src-DRRoD7Co.cjsView on unpkg · L2Findings
Affected versions and remediation
This report applies to chromatic@18.7.0.
See all versions of chromatic for other recorded verdicts.
- Review the evidence and your use of chromatic@18.7.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.