@spectrum-web-components/tray
Web component implementation of a Spectrum design Tray
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@spectrum-web-components/base | AI (dependencies): Same-monorepo sibling dependency published in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/modal | AI (dependencies): Same-monorepo sibling dependency published in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/shared | AI (dependencies): Same-monorepo sibling dependency published in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/underlay | AI (dependencies): Same-monorepo sibling dependency published in lockstep; not an independent risk. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/reactive-controllers | AI (dependencies): Same-monorepo sibling dependency published in lockstep; not an independent risk. | ai | |
| provenance | no-provenance | AI (provenance): Adobe SWC monorepo does not publish with Sigstore provenance; consistent across all versions. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.11.2 | 5 / 0 | |
| 1.11.1 | 5 / 0 | |
| 1.11.0 | 5 / 0 | |
| 1.10.0 | 5 / 0 | |
| 1.9.1 | 5 / 0 | |
| 1.7.0 | 5 / 0 | |
| 1.6.0 | 5 / 1 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.