@conform-to/react
Conform view adapter for react
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used in a Proxy trap for field metadata delegation — standard pattern for this form library, not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Package now publishes via GitHub Actions with SLSA attestation; this is the expected CI/CD publisher going forward. | ai | |
| dependencies | unvetted-dep:@conform-to/dom | AI (dependencies): Same-monorepo sibling package; versioned in lockstep with @conform-to/react, not an independent risk. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 1.19.3 | 1 / 17 | |
| 1.19.2 | 1 / 14 | |
| 1.19.1 | 1 / 14 | |
| 1.19.0 | 1 / 14 | |
| 1.18.0 | 1 / 14 | |
| 1.17.1 | 1 / 14 | |
| 1.17.0 | 1 / 14 | |
| 1.16.0 | 1 / 14 | |
| 1.15.1 | 1 / 14 | |
| 1.15.0 | 1 / 14 | |
| 1.14.1 | 1 / 14 | |
| 1.14.0 | 1 / 14 | |
| 1.13.3 | 1 / 14 | |
| 1.13.2 | 1 / 14 | |
| 1.13.1 | 1 / 14 | |
| 1.13.0 | 1 / 14 | |
| 1.12.1 | 1 / 13 | |
| 1.12.0 | 1 / 13 | |
| 1.11.0 | 1 / 13 | |
| 1.10.1 | 1 / 13 | |
| 1.10.0 | 1 / 13 | |
| 1.9.1 | 1 / 14 | |
| 1.9.0 | 1 / 14 | |
| 1.8.2 | 1 / 13 | |
| 1.8.1 | 1 / 13 | |
| 1.8.0 | 1 / 13 | |
| 1.7.2 | 1 / 13 | |
| 1.7.1 | 1 / 13 | |
| 1.7.0 | 1 / 11 | |
| 1.6.1 | 1 / 10 | |
| 1.6.0 | 1 / 10 | |
| 1.5.1 | 1 / 10 | |
| 1.5.0 | 1 / 10 |
v1.19.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
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.