chromatic@18.7.1
Automate visual testing across browsers. Gather UI feedback. Versioned documentation.
AI Security Review
scanned 19d ago · by lpm-firewall-aiInspected source does not substantiate the scanner's malicious label: the manifest has no install lifecycle hook, and flagged code maps to CLI, build, dependency-analysis, and telemetry functionality. No concrete unauthorized attack behavior was found.
Decision evidence
public snapshot- The manifest routes browser and Node exports to their package modules; no install lifecycle hook is declared.
- The Node implementation records named CLI telemetry events through its configured client, consistent with product telemetry.
- Flagged executable helpers are in CLI paths: file parsing uses a parser subprocess, and initialization asks the user to select a framework.
- Other flagged bundles import filesystem, Storybook, package-manifest, and lockfile helpers for project analysis.
- The malicious scanner label is not supported by the inspected source: the process and network matches are in CLI, build, dependency-analysis, or telemetry functionality.
- The main CLI bundle includes a platform machine-ID helper, but no invocation of that helper was found in the reviewed bundle.
Source & flagged code
10 flaggedPackage source references dynamic require/import behavior.
dist/node.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to chromatic@18.7.1.
See all versions of chromatic for other recorded verdicts.
- Review the evidence and your use of chromatic@18.7.1 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.