rc-switch
switch ui component for react
20
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
benjycuiyesmeckafc163yiminghevalleykidzombiejmadccc
Keywords
reactreact-componentreact-switchswitch
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): zombiej and afc163 are both react-component/ant-design team members; legitimate handoff. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): rc-util is the canonical utility package from the same react-component org. | ai | |
| dependencies | unvetted-dep:rc-util | AI (dependencies): rc-util is a core utility library from the same react-component/Ant Design ecosystem; its use in rc-switch is expected and stable across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established rc-* ecosystem package by trusted publisher afc163; lack of provenance attestation is common and not a meaningful risk signal here. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 3 / 20 | |
| 4.0.0 | 3 / 19 | |
| 3.2.2 | 3 / 13 | |
| 3.2.1 | 3 / 13 | |
| 3.2.0 | 3 / 13 | |
| 3.1.0 | 2 / 13 | |
| 3.0.2 | 1 / 11 | |
| 3.0.1 | 1 / 11 | |
| 3.0.0 | 1 / 11 | |
| 1.9.2 | 3 / 10 | |
| 1.9.1 | 3 / 10 | |
| 1.3.3 | 1 / 7 | |
| 1.3.2 | 1 / 7 | |
| 1.3.1 | 1 / 7 | |
| 1.3.0 | 1 / 7 | |
| 1.2.2 | 1 / 7 | |
| 1.2.1 | 1 / 5 | |
| 1.2.0 | 1 / 5 | |
| 1.1.0 | 1 / 5 | |
| 1.0.0 | 1 / 5 |
v3.1.0
2 findings
HIGH
Publisher changed: afc163 → zombiej (on 2020-05-18)
provenance
This version was published by a different npm account than previous versions on 2020-05-18. This could indicate a legitimate maintainer transition or an account compromise.
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.