@assaabloy/gw-group-featured-content
Web component - Featured Content
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
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 26.0.0 | 0 / 0 | |
| 25.0.2 | 0 / 0 | |
| 25.0.1 | 0 / 0 | |
| 25.0.0 | 0 / 0 | |
| 24.0.1 | 0 / 0 | |
| 23.1.5 | 0 / 0 | |
| 22.1.1 | 0 / 0 | |
| 22.1.0 | 0 / 0 | |
| 22.0.5 | 0 / 0 | |
| 22.0.4 | 0 / 0 | |
| 22.0.3 | 0 / 0 | |
| 22.0.2 | 0 / 0 |
v25.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.