@assaabloy/gw-group-accordion
Web component - Accordion
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): New publisher matija.vuk has approved track record and is within the same ASSAABLOY org; consistent with internal maintainer handoff. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 27.0.0 | 0 / 0 | |
| 26.0.5 | 0 / 0 | |
| 26.0.4 | 0 / 0 | |
| 26.0.3 | 0 / 0 | |
| 26.0.2 | 0 / 0 | |
| 26.0.1 | 0 / 0 | |
| 26.0.0 | 0 / 0 | |
| 25.0.1 | 0 / 0 | |
| 24.1.8 | 0 / 0 | |
| 24.1.7 | 0 / 0 | |
| 24.1.6 | 0 / 0 | |
| 24.1.5 | 0 / 0 | |
| 24.1.4 | 0 / 0 | |
| 24.1.3 | 0 / 0 | |
| 24.1.2 | 0 / 0 | |
| 24.1.1 | 0 / 0 | |
| 24.1.0 | 0 / 0 | |
| 24.0.0 | 0 / 0 | |
| 23.1.1 | 0 / 0 | |
| 23.1.0 | 0 / 0 | |
| 23.0.5 | 0 / 0 | |
| 23.0.4 | 0 / 0 | |
| 23.0.3 | 0 / 0 | |
| 23.0.2 | 0 / 0 |
v26.0.5
2 findingsThis version was published by a different npm account than previous versions on 2026-04-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.