@chromatic-com/playwright
Chromatic Visual Regression Testing for Playwright
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@chromaui/rrweb-snapshot | AI (phantom-deps): Declared runtime dep; used in browser export. Stable false positive for this package. | ai | |
| source-diff | obfuscated-file:embedded/node_modules/es-module-lexer/dist/lexer.cjs | AI (source-diff): Standard es-module-lexer distribution with WASM binary; well-known package. | ai | |
| source-diff | obfuscated-file:embedded/node_modules/baseline-browser-mapping/dist/index.cjs | AI (source-diff): Minified browser version data file; not obfuscated malware. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by inlining webpack/storybook dependencies into embedded/node_modules. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Package now bundles embedded/node_modules for self-contained storybook toolchain; large file count is structural, not injected. | ai | |
| source-diff | obfuscated-file:embedded/node_modules/webpack/node_modules/es-module-lexer/dist/lexer.cjs | AI (source-diff): es-module-lexer ships a minified WASM-backed CJS bundle by design; this is expected minification, not obfuscation. | ai | |
| source-diff | net-exec-file:embedded/node_modules/eslint-scope/dist/eslint-scope.cjs | AI (source-diff): File is the standard eslint-scope CJS bundle bundled inside embedded/node_modules; no actual network calls or malicious code in sample. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by major architectural refactor; SLSA provenance and known org repo reduce takeover risk. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation — this is a legitimate CI/CD migration for the Chromatic org. | ai | |
| provenance | no-provenance | AI (provenance): Provenance adoption is low industry-wide; not a disqualifier for established packages. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-essentials | AI (phantom-deps): Same pattern — storybook ecosystem dep used indirectly in this tooling package. | ai | |
| phantom-deps | phantom-dep:@storybook/csf | AI (phantom-deps): Same pattern — storybook ecosystem dep used indirectly in this tooling package. | ai | |
| phantom-deps | phantom-dep:storybook | AI (phantom-deps): Storybook packages are runtime deps used as tooling/config dependencies in this e2e testing package, not directly imported in source. | ai | |
| dependencies | unvetted-dep:@chromaui/rrweb-snapshot | AI (dependencies): Chromatic-owned rrweb fork; consistent with the package's DOM snapshot/visual testing purpose across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Chromatic commercial package; README structure and missing keywords are not spam indicators for this well-known tool. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.14.2 | 3 / 10 | |
| 0.14.1 | 3 / 10 | |
| 0.14.0 | 4 / 9 | |
| 0.13.4 | 4 / 9 | |
| 0.13.3 | 4 / 9 | |
| 0.13.2 | 4 / 9 | |
| 0.13.1 | 4 / 9 | |
| 0.13.0 | 4 / 9 | |
| 0.12.8 | 8 / 7 | |
| 0.12.7 | 8 / 7 | |
| 0.12.5 | 8 / 7 | |
| 0.12.4 | 8 / 7 | |
| 0.12.3 | 8 / 7 |
v0.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.1
6 findingsThis version was published by a different npm account than previous versions on 2026-04-10. This could indicate a legitimate maintainer transition or an account compromise.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
4 findingsThis version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.