chromatic@18.6.1
Automate visual testing across browsers. Gather UI feedback. Versioned documentation.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection contradicts the static malicious label: this package has no lifecycle hooks and its risky primitives are bundled CLI and dependency functionality reached through explicit commands. No concrete malicious chain was found.
Decision evidence
public snapshot- The manifest has no lifecycle scripts, so installation does not trigger package code.
- The command entry point dispatches only after the user invokes the CLI.
- The configured network service is the package-aligned Chromatic index endpoint.
- No bidi control characters were found in the flagged bundle, and no hidden payload execution was confirmed.
- The bundled CLI reads project files, environment settings, and can invoke development tools during explicit visual-test workflows.
- Bundled third-party code contains generic dynamic loading, shell, and evaluation primitives that static matching can flag.
Source & flagged code
11 flaggedSource contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/v1-BPL0QeOt.cjsView on unpkg · L30Package source references child process execution.
dist/v1-BPL0QeOt.cjsView on unpkg · L209Findings
Affected versions and remediation
This report applies to chromatic@18.6.1.
See all versions of chromatic for other recorded verdicts.
- Review the evidence and your use of chromatic@18.6.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.