rc-field-form
React Form 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): Both zombiej and afc163 are known Ant Design / react-component org maintainers. Routine rotation within the same team. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @rc-component/async-validator replaces async-validator; same org's scoped fork, standard pattern in react-component ecosystem. | ai |
Versions (showing 18 of 118)
| Version | Deps | Published |
|---|---|---|
| 1.4.3 | 3 / 18 | |
| 1.4.2 | 3 / 18 | |
| 1.4.1 | 3 / 18 | |
| 1.4.0 | 3 / 18 | |
| 1.3.0 | 3 / 18 | |
| 1.2.4 | 3 / 18 | |
| 1.2.3 | 3 / 17 | |
| 1.2.2 | 3 / 17 | |
| 1.2.1 | 3 / 17 | |
| 1.2.0 | 3 / 17 | |
| 1.1.3 | 4 / 17 | |
| 1.1.2 | 4 / 17 | |
| 1.1.1 | 4 / 17 | |
| 1.1.0 | 4 / 17 | |
| 1.0.1 | 4 / 17 | |
| 1.0.0 | 4 / 17 | |
| 0.0.1 | 4 / 17 | |
| 0.0.0 | 5 / 11 |
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.