@not-govuk/details
A component to make a page easier to scan by letting users reveal more detailed information only if they need it.
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 | no-provenance | AI (provenance): Consistent across all 84 versions of this package; no provenance is the norm for this publisher. | ai | |
| phantom-deps | phantom-dep:govuk-frontend | AI (phantom-deps): Referenced in SCSS/config, not JS imports; stable false positive for this UI component package. | ai | |
| phantom-deps | phantom-dep:@not-govuk/sass-base | AI (phantom-deps): Same-org SCSS dependency; phantom-dep heuristic fires on SCSS imports, not a real concern. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 3 / 6 | |
| 0.18.0 | 3 / 6 | |
| 0.17.4 | 3 / 6 | |
| 0.17.3 | 3 / 6 | |
| 0.17.2 | 3 / 6 | |
| 0.17.1 | 3 / 6 | |
| 0.17.0 | 3 / 6 | |
| 0.16.3 | 3 / 7 | |
| 0.16.0 | 3 / 7 | |
| 0.15.13 | 3 / 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.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. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.