chromatic@18.12.2
Automate visual testing across browsers. Gather UI feedback. Versioned documentation.
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe source inspected supports ordinary Chromatic CLI and browser-helper behavior. Scanner flags for bundled process and network primitives did not establish credential disclosure, hidden execution, or unconsented mutation.
Decision evidence
public snapshot- package.json exposes a Chromatic CLI and a separate browser helper.
- The browser helper only checks the browser user agent and URL for Chromatic markers.
- The main bundle’s Sentry initialization is disabled by a constant-false condition.
- The flagged projectFiles, node-src, build, and v1 files are bundled CLI chunks; inspected excerpts show module assembly.
- The init bundle exposes project setup through the explicit `chromatic init` command.
- The execa chunk provides ordinary child-process spawn helpers for CLI use.
- The bundles include process execution and HTTP code, but the inspected excerpts do not establish hidden execution, credential transfer, or an unrelated recipient.
- The init code can add a `chromatic` project script, but this is part of the explicit init command.
Source & flagged code
10 flaggedPackage source references child process execution.
dist/main-BNmoik4g.cjsView on unpkg · L2Findings
Affected versions and remediation
This report applies to chromatic@18.12.2.
See all versions of chromatic for other recorded verdicts.
- Review the evidence and your use of chromatic@18.12.2 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.