polendina
Non-UI browser testing for JavaScript libraries from the command-line
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:raw-loader | AI (phantom-deps): Webpack loader referenced in config, not direct import; stable pattern. | ai | |
| phantom-deps | phantom-dep:path-browserify | AI (phantom-deps): Webpack polyfill referenced in config, not direct import; stable pattern. | ai | |
| phantom-deps | phantom-dep:readable-stream | AI (phantom-deps): Webpack polyfill referenced in config, not direct import; stable pattern. | ai | |
| phantom-deps | phantom-dep:stream-browserify | AI (phantom-deps): Webpack polyfill referenced in config, not direct import; stable pattern. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.2.21 | 14 / 1 | |
| 3.2.20 | 14 / 1 | |
| 3.2.19 | 14 / 1 | |
| 3.2.18 | 14 / 1 | |
| 3.2.17 | 14 / 1 | |
| 3.2.16 | 14 / 1 | |
| 3.2.15 | 14 / 1 | |
| 3.2.14 | 14 / 1 | |
| 3.2.13 | 14 / 1 | |
| 3.2.12 | 14 / 1 | |
| 3.2.11 | 14 / 1 |
v3.2.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.