rc-upload
upload 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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from zombiej to afc163 is a routine rotation within the react-component/ant-design team. Both are established maintainers. | ai | |
| provenance | no-provenance | AI (provenance): Informational only; rc-upload predates widespread Sigstore adoption. No security concern. | ai |
Versions (showing 51 of 127)
| Version | Deps | Published |
|---|---|---|
| 4.11.0 | 3 / 25 | |
| 4.10.0 | 3 / 25 | |
| 4.9.2 | 3 / 25 | |
| 4.9.1 | 3 / 25 | |
| 4.9.0 | 3 / 25 | |
| 4.8.1 | 3 / 25 | |
| 4.8.0 | 3 / 25 | |
| 4.7.0 | 3 / 25 | |
| 4.6.0 | 3 / 25 | |
| 4.5.2 | 3 / 26 | |
| 4.5.1 | 3 / 26 | |
| 4.4.0 | 3 / 26 | |
| 4.3.6 | 3 / 26 | |
| 4.3.5 | 3 / 26 | |
| 4.3.4 | 3 / 26 | |
| 4.3.3 | 3 / 26 | |
| 4.3.2 | 3 / 26 | |
| 4.3.1 | 3 / 26 | |
| 4.3.0 | 3 / 26 | |
| 4.2.1 | 3 / 26 | |
| 4.2.0 | 3 / 26 | |
| 4.1.0 | 3 / 26 | |
| 4.0.1 | 3 / 26 | |
| 4.0.0 | 3 / 26 | |
| 3.3.4 | 3 / 24 | |
| 3.3.3 | 3 / 24 | |
| 3.3.2 | 3 / 24 | |
| 3.3.1 | 3 / 23 | |
| 3.3.0 | 3 / 23 | |
| 3.2.1 | 1 / 14 | |
| 3.2.0 | 1 / 14 | |
| 3.1.4 | 1 / 14 | |
| 3.1.3 | 1 / 14 | |
| 3.1.2 | 1 / 14 | |
| 3.1.1 | 1 / 14 | |
| 3.1.0 | 2 / 14 | |
| 3.0.4 | 2 / 14 | |
| 3.0.3 | 2 / 14 | |
| 3.0.2 | 2 / 14 | |
| 3.0.1 | 2 / 14 | |
| 3.0.0 | 2 / 14 | |
| 2.9.4 | 4 / 11 | |
| 2.9.3 | 4 / 11 | |
| 2.9.2 | 4 / 11 | |
| 2.9.1 | 4 / 11 | |
| 2.9.0 | 4 / 11 | |
| 2.8.1 | 4 / 11 | |
| 2.8.0 | 4 / 11 | |
| 2.7.0 | 4 / 11 | |
| 2.6.8 | 4 / 11 | |
| 2.6.7 | 4 / 11 |
v4.5.2
2 findingsThis version was published by a different npm account than previous versions on 2023-12-21. 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.
v4.5.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-12-13. This could indicate a legitimate maintainer transition or an account compromise.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-12-22. This could indicate a legitimate maintainer transition or an account compromise.
v4.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-05-26. This could indicate a legitimate maintainer transition or an account compromise.
v4.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
2 findingsThis version was published by a different npm account than previous versions on 2021-10-20. 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.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-03-24. This could indicate a legitimate maintainer transition or an account compromise.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2021-03-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.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-09-07. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-08-31. This could indicate a legitimate maintainer transition or an account compromise.
v3.2.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-08-29. This could indicate a legitimate maintainer transition or an account compromise.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-06-09. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-06-02. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-10. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-02-26. This could indicate a legitimate maintainer transition or an account compromise.