@not-govuk/form
A component to collect information from the user.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@not-govuk/component-helpers | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Established GovUK design system component; name similarity to 'cors' is coincidental. | ai | |
| phantom-deps | phantom-dep:@react-foundry/component-helpers | AI (phantom-deps): Declared runtime dependency; indirect import pattern is normal for component libraries. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 12 / 7 | |
| 0.18.0 | 12 / 7 | |
| 0.17.4 | 12 / 7 | |
| 0.17.3 | 12 / 7 | |
| 0.17.2 | 12 / 7 | |
| 0.17.1 | 12 / 7 | |
| 0.17.0 | 12 / 7 | |
| 0.16.3 | 12 / 8 | |
| 0.16.2 | 12 / 8 |
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.