@shopgate/pwa-unit-test
The unit tests setup for Shopgate's ENGAGE.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:babel-core | AI (phantom-deps): Test-setup package; config-file references are expected for Jest/Babel tooling. | ai | |
| phantom-deps | phantom-dep:identity-obj-proxy | AI (phantom-deps): Test-setup package; config-file references are expected for Jest/Babel tooling. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established internal tool; weak signals for a 1170-version package with 30 prior approvals. | ai | |
| phantom-deps | phantom-dep:cheerio | AI (phantom-deps): Declared as runtime dependency; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:enzyme-to-json | AI (phantom-deps): Declared as runtime dependency; heuristic false positive for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 7.30.4 | 4 / 9 | |
| 7.30.3 | 4 / 9 | |
| 7.30.2 | 4 / 9 | |
| 7.30.1 | 4 / 9 | |
| 7.30.0 | 4 / 9 | |
| 7.29.9 | 7 / 7 | |
| 7.29.8 | 7 / 7 | |
| 7.29.7 | 7 / 7 | |
| 7.29.6 | 7 / 7 | |
| 7.29.5 | 7 / 7 | |
| 7.29.4 | 7 / 7 | |
| 7.29.3 | 7 / 7 | |
| 7.29.1 | 7 / 7 | |
| 7.29.0 | 7 / 7 | |
| 7.28.3 | 7 / 7 | |
| 7.28.2 | 7 / 7 | |
| 7.28.1 | 7 / 7 | |
| 7.28.0 | 7 / 7 | |
| 7.27.5 | 7 / 7 | |
| 7.27.4 | 7 / 7 | |
| 7.27.3 | 7 / 7 | |
| 7.27.2 | 7 / 7 | |
| 7.27.1 | 7 / 7 | |
| 7.27.0 | 7 / 7 | |
| 7.26.0 | 7 / 7 | |
| 7.25.1 | 7 / 7 | |
| 7.24.8 | 7 / 7 |
v7.30.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.28.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.