@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 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 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 |
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
2 findingsThis version was published by a different npm account than previous versions on 2026-02-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
2 findingsThis version was published by a different npm account than previous versions on 2025-09-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
2 findingsThis version was published by a different npm account than previous versions on 2025-06-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.