@spectrum-web-components/swatch
Web component implementation of a Spectrum design Swatch
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): Sibling monorepo package from Adobe; same versioning pattern across all SWC packages. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/icon | AI (dependencies): Sibling monorepo package from Adobe; same versioning pattern across all SWC packages. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/shared | AI (dependencies): Sibling monorepo package from Adobe; same versioning pattern across all SWC packages. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/icons-ui | AI (dependencies): Sibling monorepo package from Adobe; same versioning pattern across all SWC packages. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/opacity-checkerboard | AI (dependencies): Sibling monorepo package from Adobe; same versioning pattern across all SWC packages. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/reactive-controllers | AI (dependencies): Sibling monorepo package from Adobe; same versioning pattern across all SWC packages. | ai | |
| provenance | no-provenance | AI (provenance): Adobe SWC monorepo does not publish with Sigstore provenance; consistent across all versions. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.11.2 | 7 / 0 | |
| 1.11.1 | 7 / 0 | |
| 1.11.0 | 7 / 0 | |
| 1.10.0 | 7 / 0 | |
| 1.9.1 | 7 / 0 | |
| 1.6.0 | 7 / 2 | |
| 1.1.0 | 7 / 2 | |
| 1.0.3 | 7 / 2 | |
| 1.0.2 | 7 / 2 | |
| 1.0.1 | 7 / 2 | |
| 1.0.0 | 7 / 2 |
v1.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rajrock38) than the most recent previously approved version (rubenc) on 2025-01-29, but rajrock38 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rubenc) than the most recent previously approved version (rajrock38) on 2024-12-09, but rubenc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pvashish) than the most recent previously approved version (rajrock38) on 2024-11-26, but pvashish is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rajrock38) than the most recent previously approved version (rubenc) on 2024-11-11, but rajrock38 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.