@spectrum-web-components/sidenav
Side navigation allows users to locate information and features within the UI. It can be used for either hierarchical or flat navigation, and gives the ability to group navigable items categorically. Side navigation is an opportunity to prioritize content
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Adobe monorepo migrated publishing to GitHub Actions CI; SLSA attestation confirms legitimate automated release pipeline. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are consistent with Adobe org team changes; SLSA provenance confirms CI-controlled publish. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/reactive-controllers | AI (dependencies): Same-monorepo sibling package from Adobe; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Adobe's spectrum-web-components monorepo does not publish with Sigstore provenance; stable pattern across all versions. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.12.1 | 3 / 0 | |
| 1.12.0 | 3 / 0 | |
| 1.11.2 | 3 / 0 | |
| 1.11.1 | 3 / 0 | |
| 1.11.0 | 3 / 0 | |
| 1.10.0 | 3 / 0 | |
| 1.9.1 | 3 / 0 | |
| 1.9.0 | 3 / 0 | |
| 1.8.0 | 3 / 0 | |
| 1.7.0 | 3 / 0 | |
| 1.6.0 | 3 / 1 |
v1.12.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-13. 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.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.