@spectrum-web-components/overlay
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@spectrum-web-components/theme | AI (phantom-deps): Same-org monorepo dep; declared for peer/type resolution, not a direct import. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/action-button | AI (phantom-deps): Same-org monorepo dep; declared for peer/type resolution, not a direct import. | ai | |
| phantom-deps | phantom-dep:@floating-ui/utils | AI (phantom-deps): Transitive floating-ui dep declared explicitly for version pinning; stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.12.1 | 8 / 0 | |
| 1.12.0 | 8 / 0 | |
| 1.11.2 | 8 / 0 | |
| 1.11.1 | 8 / 0 | |
| 1.11.0 | 8 / 0 | |
| 1.10.0 | 8 / 0 | |
| 1.9.1 | 8 / 0 | |
| 1.9.0 | 8 / 0 | |
| 1.8.0 | 8 / 0 | |
| 1.7.0 | 8 / 0 | |
| 1.6.0 | 8 / 0 |
v1.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.0
1 findingPublished 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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.