rc-input-number
React input-number component
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): afc163 is a known long-standing maintainer in the react-component/ant-design ecosystem; this is a routine team transition. | ai |
Versions (showing 51 of 208)
| Version | Deps | Published |
|---|---|---|
| 9.5.0 | 5 / 31 | |
| 9.4.0 | 5 / 31 | |
| 9.3.0 | 5 / 31 | |
| 9.2.0 | 5 / 31 | |
| 9.1.0 | 5 / 31 | |
| 9.0.0 | 5 / 31 | |
| 8.6.1 | 5 / 29 | |
| 8.6.0 | 5 / 29 | |
| 8.5.0 | 5 / 29 | |
| 8.4.0 | 5 / 29 | |
| 8.3.0 | 5 / 29 | |
| 8.2.0 | 5 / 29 | |
| 8.1.0 | 5 / 29 | |
| 8.0.4 | 5 / 29 | |
| 8.0.3 | 5 / 29 | |
| 8.0.2 | 5 / 29 | |
| 8.0.1 | 5 / 29 | |
| 8.0.0 | 5 / 29 | |
| 7.4.2 | 4 / 29 | |
| 7.4.1 | 4 / 29 | |
| 7.4.0 | 4 / 23 | |
| 7.3.11 | 3 / 23 | |
| 7.3.9 | 3 / 23 | |
| 7.3.8 | 3 / 23 | |
| 7.3.7 | 3 / 23 | |
| 7.3.6 | 3 / 22 | |
| 7.3.5 | 3 / 22 | |
| 7.3.4 | 3 / 23 | |
| 7.3.3 | 3 / 23 | |
| 7.3.2 | 3 / 23 | |
| 7.3.1 | 3 / 23 | |
| 7.3.0 | 3 / 23 | |
| 7.2.0 | 3 / 23 | |
| 7.1.4 | 3 / 23 | |
| 7.1.3 | 3 / 23 | |
| 7.1.2 | 3 / 23 | |
| 7.1.1 | 3 / 23 | |
| 7.1.0 | 3 / 23 | |
| 7.0.6 | 3 / 23 | |
| 7.0.5 | 3 / 23 | |
| 7.0.4 | 3 / 23 | |
| 7.0.3 | 3 / 23 | |
| 7.0.2 | 3 / 23 | |
| 7.0.1 | 3 / 23 | |
| 7.0.0 | 3 / 23 | |
| 6.2.0 | 3 / 21 | |
| 6.1.3 | 3 / 21 | |
| 6.1.2 | 3 / 19 | |
| 6.1.1 | 3 / 19 | |
| 6.1.0 | 3 / 19 | |
| 6.0.1 | 3 / 19 |
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
2 findingsPackage 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-15. This could indicate a legitimate maintainer transition or an account compromise.
v8.5.0
2 findingsThis version was published by a different npm account than previous versions on 2023-10-29. 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.
v8.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
2 findingsPackage 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-08-01. This could indicate a legitimate maintainer transition or an account compromise.
v8.0.3
2 findingsPackage 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-07-19. This could indicate a legitimate maintainer transition or an account compromise.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.