@spectrum-web-components/alert-banner
Web component implementation of a Spectrum design AlertBanner
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party Adobe package in the same monorepo; not a supply-chain risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Large Adobe org project; maintainer additions are routine team changes, not suspicious takeover signals. | ai | |
| provenance | no-provenance | AI (provenance): Adobe monorepo package; lack of provenance is consistent across the entire @spectrum-web-components namespace. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/base | AI (dependencies): Sibling package in Adobe's spectrum-web-components monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/icons-workflow | AI (dependencies): Sibling package in Adobe's spectrum-web-components monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/core | AI (dependencies): Sibling package in Adobe's spectrum-web-components monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/button | AI (dependencies): Sibling package in Adobe's spectrum-web-components monorepo; stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.12.1 | 3 / 0 | |
| 1.12.0 | 3 / 0 | |
| 1.11.2 | 4 / 0 | |
| 1.11.1 | 4 / 0 | |
| 1.11.0 | 4 / 0 | |
| 1.10.0 | 4 / 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
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. Consider requesting the maintainer enable provenance via CI/CD.
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.