@shopgate/pwa-core
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared in dependencies; used indirectly via config/transitive imports. | ai | |
| phantom-deps | phantom-dep:detector | AI (phantom-deps): Declared in dependencies; used indirectly via config/transitive imports. | ai | |
| phantom-deps | phantom-dep:crypto-js | AI (phantom-deps): Declared in dependencies; used indirectly via config/transitive imports. | ai | |
| phantom-deps | phantom-dep:mobile-detect | AI (phantom-deps): Declared in dependencies; used indirectly via config/transitive imports. | ai | |
| phantom-deps | phantom-dep:isomorphic-fetch | AI (phantom-deps): Declared in dependencies; used indirectly via config/transitive imports. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package; no provenance is consistent across all versions and is not a risk indicator here. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 7.30.4 | 4 / 0 | |
| 7.30.3 | 4 / 0 | |
| 7.30.2 | 4 / 0 | |
| 7.30.1 | 4 / 0 | |
| 7.30.0 | 4 / 0 | |
| 7.29.9 | 5 / 0 | |
| 7.29.8 | 5 / 0 | |
| 7.29.7 | 5 / 0 | |
| 7.29.6 | 5 / 0 | |
| 7.29.5 | 5 / 0 | |
| 7.29.4 | 5 / 0 | |
| 7.29.3 | 5 / 0 | |
| 7.29.1 | 5 / 0 | |
| 7.29.0 | 5 / 0 | |
| 7.28.3 | 5 / 0 | |
| 7.28.2 | 5 / 0 | |
| 7.28.1 | 5 / 0 | |
| 7.28.0 | 5 / 0 | |
| 7.27.5 | 5 / 0 | |
| 7.27.4 | 5 / 0 | |
| 7.27.3 | 5 / 0 | |
| 7.27.2 | 5 / 0 | |
| 7.27.1 | 5 / 0 | |
| 7.27.0 | 5 / 0 | |
| 7.26.0 | 5 / 0 | |
| 7.25.1 | 5 / 0 | |
| 7.24.8 | 5 / 0 |
v7.30.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.