← Home

@spectrum-web-components/slider

npm Repository Homepage

`<sp-slider>` allows users to quickly select a value within a range. They should be used when the upper and lower bounds of the range are invariable.

12
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

caseyisonittaratadoberajrock38jnjoshnikkimkrubencjianliao79pvashishpatrickfulton

Keywords

design-systemspectrumadobeadobe-spectrumweb componentsweb-componentslit-elementlit-htmlcomponentcss

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@spectrum-web-components/theme AI (phantom-deps): Same-org monorepo sibling; declared as peer/dep for theming side-effects, not necessarily directly imported. ai

Versions (showing 12 of 12)

Version Deps Published
1.11.2 8 / 0
1.11.1 8 / 0
1.11.0 8 / 0
1.9.0 8 / 0
1.8.0 8 / 0
1.7.0 8 / 0
1.6.0 8 / 1
1.1.0 8 / 1
1.0.3 8 / 1
1.0.2 8 / 1
1.0.1 8 / 1
1.0.0 8 / 1

v1.1.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: pvashish → rajrock38 (on 2025-01-29, known maintainer) provenance

This version was published by a different npm account (rajrock38) than the most recent previously approved version (pvashish) 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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: pvashish → rubenc (on 2024-12-09, known maintainer) provenance

This version was published by a different npm account (rubenc) than the most recent previously approved version (pvashish) 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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: rajrock38 → pvashish (on 2024-11-26, known maintainer) provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: rubenc → rajrock38 (on 2024-11-11, known maintainer) provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.