@shopgate/pwa-ui-material
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:react-transition-group | AI (phantom-deps): Transition library; used indirectly in component implementations. | ai | |
| phantom-deps | phantom-dep:color | AI (phantom-deps): UI library dependency; used indirectly in component styling. | ai | |
| phantom-deps | phantom-dep:glamor | AI (phantom-deps): CSS-in-JS library for Material Design components; stable pattern. | ai | |
| phantom-deps | phantom-dep:react-use | AI (phantom-deps): React hooks library; used indirectly in component implementations. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Utility for conditional CSS classes; standard in UI libraries. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): React prop validation; used indirectly in component definitions. | ai | |
| phantom-deps | phantom-dep:react-spring | AI (phantom-deps): Animation library for Material Design; used indirectly in components. | ai | |
| provenance | no-provenance | AI (provenance): Established Shopgate monorepo package; no provenance is consistent across all prior versions. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 7.30.4 | 7 / 4 | |
| 7.30.3 | 7 / 4 | |
| 7.30.2 | 7 / 4 | |
| 7.30.1 | 7 / 4 | |
| 7.30.0 | 7 / 4 | |
| 7.29.9 | 7 / 4 | |
| 7.29.8 | 7 / 4 | |
| 7.29.7 | 7 / 4 | |
| 7.29.6 | 7 / 4 | |
| 7.29.5 | 7 / 4 | |
| 7.29.4 | 7 / 4 | |
| 7.29.3 | 7 / 4 | |
| 7.29.1 | 7 / 4 | |
| 7.29.0 | 7 / 4 | |
| 7.28.3 | 7 / 4 | |
| 7.28.2 | 7 / 4 | |
| 7.28.1 | 7 / 4 | |
| 7.28.0 | 7 / 4 | |
| 7.27.5 | 7 / 4 | |
| 7.27.4 | 7 / 4 | |
| 7.27.3 | 7 / 4 | |
| 7.27.2 | 7 / 4 | |
| 7.27.1 | 7 / 4 | |
| 7.27.0 | 7 / 4 | |
| 7.26.0 | 7 / 4 | |
| 7.25.1 | 7 / 4 | |
| 7.24.8 | 7 / 4 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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.