@not-govuk/text-input
A single line text field.
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:@not-govuk/input | AI (dependencies): Same-namespace sibling dep from the same author; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@not-govuk/form-group | AI (dependencies): Same-namespace sibling dep from the same author; stable pattern across all versions. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 2 / 6 | |
| 0.18.0 | 2 / 6 | |
| 0.17.4 | 2 / 6 | |
| 0.17.3 | 2 / 6 | |
| 0.17.2 | 2 / 6 | |
| 0.17.1 | 2 / 6 | |
| 0.17.0 | 2 / 6 | |
| 0.16.3 | 2 / 7 | |
| 0.16.2 | 2 / 7 | |
| 0.16.1 | 2 / 7 | |
| 0.16.0 | 2 / 7 | |
| 0.15.14 | 2 / 7 |
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.