@not-govuk/tag MIT 10 versions

@not-govuk/tag

npm

A component to display the status of something.

10

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

daniel-ac-martin

Keywords

react-components

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Established org package; lack of provenance is consistent across all @not-govuk/* releases.	ai	2026/05/09
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped package @not-govuk/tag is a GOV.UK component; no relation to pg (postgres client). Levenshtein match is spurious.	ai	2026/04/29
phantom-deps	phantom-dep:govuk-frontend	AI (phantom-deps): govuk-frontend is used via SCSS imports in assets/, not JS imports; phantom-dep heuristic doesn't cover SCSS usage.	ai	2026/04/29
phantom-deps	phantom-dep:@not-govuk/sass-base	AI (phantom-deps): Same-org SCSS dependency; used in stylesheet assets, not JS imports. False positive for this package.	ai	2026/04/29

Versions (showing 10 of 10)

Version	Deps	Published
0.18.1	3 / 7	2026-04-26
0.18.0	3 / 7	2026-04-26
0.17.4	3 / 7	2026-04-09
0.17.3	3 / 7	2026-02-03
0.17.2	3 / 7	2026-02-02
0.17.1	3 / 7	2026-01-29
0.17.0	3 / 7	2026-01-29
0.16.2	3 / 8	2025-05-30
0.15.14	3 / 8	2025-05-08
0.15.13	3 / 8	2025-05-07

v0.18.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.17.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.17.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.15.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.15.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.