← Home

@not-govuk/link

npm

A drop-in replacement for the 'a' element with GovUK styling.

9
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.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@not-govuk/anchor AI (dependencies): Same-org dependency consistent with the @not-govuk component library pattern; stable across versions. ai
typosquat typosquat.levenshtein:pino AI (typosquat): Package is part of the @not-govuk org scope; no relation to pino. False positive. ai
phantom-deps phantom-dep:govuk-frontend AI (phantom-deps): govuk-frontend is a SCSS dependency referenced in assets, not a JS import. Expected pattern for this component library. ai
phantom-deps phantom-dep:@not-govuk/sass-base AI (phantom-deps): Same-org SCSS base dependency; not a JS import by design. ai

Versions (showing 9 of 9)

Version Deps Published
0.18.1 3 / 8
0.18.0 3 / 8
0.17.4 3 / 8
0.17.3 3 / 8
0.17.2 3 / 8
0.17.1 3 / 8
0.17.0 3 / 8
0.16.2 3 / 9
0.15.14 3 / 9

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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.