rc-slider
Slider UI component for React
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:rc-util | AI (dependencies): rc-util is the standard shared utility library for the react-component ecosystem; its use in rc-slider is expected and stable across all versions. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.1.9 | 3 / 27 | |
| 11.1.8 | 3 / 27 | |
| 11.1.7 | 3 / 27 | |
| 11.1.6 | 3 / 27 | |
| 11.1.5 | 3 / 27 | |
| 11.1.3 | 3 / 27 | |
| 11.1.2 | 3 / 27 | |
| 11.1.1 | 3 / 27 | |
| 11.1.0 | 3 / 27 | |
| 11.0.6 | 3 / 27 | |
| 11.0.5 | 3 / 27 | |
| 11.0.2 | 3 / 27 | |
| 11.0.1 | 3 / 27 | |
| 11.0.0 | 3 / 27 | |
| 10.5.0 | 3 / 24 |
v11.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (afc163) than the most recent previously approved version (zombiej) on 2024-09-17, but afc163 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.
v11.1.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (afc163) than the most recent previously approved version (zombiej) on 2024-07-25, but afc163 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.
v11.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zombiej) than the most recent previously approved version (madccc) on 2024-07-20, but zombiej 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.
v11.0.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zombiej) than the most recent previously approved version (madccc) on 2024-07-18, but zombiej 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.
v11.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zombiej) than the most recent previously approved version (madccc) on 2024-07-18, but zombiej 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.
v11.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zombiej) than the most recent previously approved version (madccc) on 2024-07-17, but zombiej 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.
v11.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zombiej) than the most recent previously approved version (madccc) on 2024-07-17, but zombiej 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.