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 100 of 118)
| Version | Deps | Published |
|---|---|---|
| 2.7.1 | 3 / 26 | |
| 2.7.0 | 3 / 26 | |
| 2.6.0 | 3 / 26 | |
| 2.5.1 | 3 / 26 | |
| 2.5.0 | 3 / 26 | |
| 2.4.0 | 3 / 26 | |
| 2.3.0 | 3 / 26 | |
| 2.2.1 | 3 / 26 | |
| 2.2.0 | 3 / 26 | |
| 2.1.0 | 3 / 26 | |
| 2.0.1 | 3 / 26 | |
| 2.0.0 | 3 / 26 | |
| 1.44.0 | 3 / 26 | |
| 1.43.0 | 3 / 25 | |
| 1.42.1 | 3 / 25 | |
| 1.42.0 | 3 / 25 | |
| 1.41.0 | 3 / 25 | |
| 1.40.0 | 3 / 23 | |
| 1.39.0 | 3 / 23 | |
| 1.38.2 | 3 / 23 | |
| 1.38.1 | 3 / 23 | |
| 1.38.0 | 3 / 23 | |
| 1.37.0 | 3 / 27 | |
| 1.36.2 | 3 / 27 | |
| 1.36.1 | 3 / 27 | |
| 1.36.0 | 3 / 27 | |
| 1.35.0 | 3 / 27 | |
| 1.34.2 | 3 / 27 | |
| 1.34.1 | 3 / 27 | |
| 1.34.0 | 3 / 27 | |
| 1.33.0 | 3 / 27 | |
| 1.32.2 | 3 / 27 | |
| 1.32.1 | 3 / 27 | |
| 1.32.0 | 3 / 27 | |
| 1.31.0 | 3 / 27 | |
| 1.30.0 | 3 / 27 | |
| 1.29.2 | 3 / 27 | |
| 1.29.1 | 3 / 27 | |
| 1.29.0 | 3 / 27 | |
| 1.28.0 | 3 / 27 | |
| 1.27.4 | 3 / 27 | |
| 1.27.3 | 3 / 26 | |
| 1.27.2 | 3 / 26 | |
| 1.27.1 | 3 / 26 | |
| 1.27.0 | 3 / 27 | |
| 1.26.7 | 3 / 25 | |
| 1.26.6 | 3 / 25 | |
| 1.26.5 | 3 / 25 | |
| 1.26.4 | 3 / 25 | |
| 1.26.3 | 3 / 25 | |
| 1.26.2 | 3 / 25 | |
| 1.26.1 | 3 / 25 | |
| 1.26.0 | 3 / 25 | |
| 1.25.2 | 3 / 25 | |
| 1.25.1 | 3 / 25 | |
| 1.25.0 | 3 / 25 | |
| 1.24.0 | 3 / 25 | |
| 1.23.1 | 3 / 25 | |
| 1.23.0 | 3 / 25 | |
| 1.22.1 | 3 / 25 | |
| 1.22.0 | 3 / 25 | |
| 1.21.2 | 3 / 25 | |
| 1.21.1 | 3 / 25 | |
| 1.21.0 | 3 / 25 | |
| 1.20.1 | 3 / 25 | |
| 1.20.0 | 3 / 25 | |
| 1.19.0 | 3 / 25 | |
| 1.18.1 | 3 / 25 | |
| 1.18.0 | 3 / 25 | |
| 1.17.4 | 3 / 23 | |
| 1.17.3 | 3 / 23 | |
| 1.17.2 | 3 / 23 | |
| 1.17.1 | 3 / 23 | |
| 1.17.0 | 3 / 23 | |
| 1.16.0 | 3 / 23 | |
| 1.15.1 | 3 / 19 | |
| 1.15.0 | 3 / 19 | |
| 1.14.0 | 3 / 19 | |
| 1.13.2 | 3 / 18 | |
| 1.13.1 | 3 / 18 | |
| 1.13.0 | 3 / 18 | |
| 1.12.1 | 3 / 18 | |
| 1.12.0 | 3 / 18 | |
| 1.11.1 | 3 / 18 | |
| 1.11.0 | 3 / 18 | |
| 1.10.1 | 3 / 18 | |
| 1.10.0 | 3 / 18 | |
| 1.9.4 | 3 / 18 | |
| 1.9.3 | 3 / 18 | |
| 1.9.2 | 3 / 18 | |
| 1.9.1 | 3 / 18 | |
| 1.9.0 | 3 / 18 | |
| 1.8.1 | 3 / 18 | |
| 1.8.0 | 3 / 18 | |
| 1.7.1 | 3 / 18 | |
| 1.7.0 | 3 / 18 | |
| 1.6.0 | 3 / 18 | |
| 1.5.1 | 3 / 18 | |
| 1.5.0 | 3 / 18 | |
| 1.4.4 | 3 / 18 |
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2024-04-16. 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.
v1.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.2
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-09-22. This could indicate a legitimate maintainer transition or an account compromise.
v1.38.1
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-09-19. This could indicate a legitimate maintainer transition or an account compromise.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.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-06-25. This could indicate a legitimate maintainer transition or an account compromise.
v1.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.2
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 2022-09-27. This could indicate a legitimate maintainer transition or an account compromise.
v1.27.1
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 2022-07-13. This could indicate a legitimate maintainer transition or an account compromise.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.