@not-govuk/file-upload
A component to help users select and upload a file.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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/sass-base | AI (phantom-deps): Same-org SCSS dependency; declared for consumers but not directly imported in JS — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:govuk-frontend | AI (phantom-deps): govuk-frontend is referenced in SCSS/config files, not JS imports; phantom-dep false positive for this UI component package. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 4 / 6 | |
| 0.18.0 | 4 / 6 | |
| 0.17.4 | 4 / 6 | |
| 0.17.3 | 4 / 6 | |
| 0.17.2 | 4 / 6 | |
| 0.17.1 | 4 / 6 | |
| 0.17.0 | 4 / 6 | |
| 0.16.3 | 4 / 7 | |
| 0.16.2 | 4 / 7 | |
| 0.16.1 | 4 / 7 | |
| 0.16.0 | 4 / 7 | |
| 0.15.14 | 4 / 7 | |
| 0.15.12 | 4 / 7 | |
| 0.15.11 | 4 / 7 | |
| 0.15.10 | 4 / 7 | |
| 0.15.9 | 4 / 7 | |
| 0.15.8 | 4 / 7 | |
| 0.15.7 | 4 / 7 | |
| 0.15.6 | 4 / 7 | |
| 0.15.5 | 4 / 7 | |
| 0.15.4 | 4 / 7 | |
| 0.15.3 | 4 / 7 | |
| 0.15.2 | 4 / 7 | |
| 0.15.1 | 4 / 7 | |
| 0.15.0 | 4 / 7 | |
| 0.8.6 | 5 / 7 | |
| 0.8.5 | 5 / 7 | |
| 0.8.4 | 5 / 7 | |
| 0.8.3 | 5 / 7 | |
| 0.8.2 | 5 / 7 | |
| 0.8.1 | 5 / 7 | |
| 0.8.0 | 5 / 7 | |
| 0.7.2 | 5 / 7 | |
| 0.7.1 | 5 / 7 | |
| 0.7.0 | 5 / 7 | |
| 0.6.0 | 5 / 7 |
v0.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.