@rc-component/input
React input 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@rc-component/resize-observer | AI (dependencies): @rc-component/resize-observer is a sibling package in the same react-component/Ant Design org, published by the same trusted maintainer group. Not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm packages lack it); this is a legitimate rc-component org package with a clear GitHub repo. Not a meaningful risk signal here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 3 / 23 | |
| 1.3.0 | 3 / 23 | |
| 1.2.1 | 2 / 23 | |
| 1.2.0 | 2 / 23 | |
| 1.1.2 | 2 / 23 | |
| 1.1.1 | 2 / 25 | |
| 1.1.0 | 2 / 25 | |
| 1.0.1 | 2 / 25 | |
| 1.0.0 | 2 / 25 |
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.