@spectrum-web-components/color-slider
An `<sp-color-slider>` lets users visually change an individual channel of a color. The background of the `<sp-color-slider>` is a visual representation of the range of values a user can select from. This can represent color properties such as hues, color
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Adobe org package; adding maintainers is routine for this large open-source project. | ai | |
| provenance | publisher-changed | AI (provenance): rubenc is an established Adobe publisher (684 approved, 0 rejected); transition within Adobe org is expected for this monorepo. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/color-handle | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/opacity-checkerboard | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/base | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Adobe monorepo package; no provenance is consistent across all versions of this package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/reactive-controllers | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/shared | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.12.2 | 5 / 0 | |
| 1.12.1 | 5 / 0 | |
| 1.12.0 | 5 / 0 | |
| 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.9.0 | 5 / 0 | |
| 1.8.0 | 5 / 0 | |
| 1.7.0 | 5 / 0 | |
| 1.6.0 | 5 / 1 | |
| 1.1.0 | 6 / 1 | |
| 1.0.3 | 6 / 1 | |
| 1.0.2 | 6 / 1 | |
| 1.0.1 | 6 / 1 | |
| 1.0.0 | 6 / 1 |
v1.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.