← Home

@not-govuk/service-navigation

npm

A component to help users understand that they’re using your service and lets them navigate around your service.

22
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

daniel-ac-martin

Keywords

react-components

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:govuk-frontend AI (phantom-deps): govuk-frontend is a SASS/CSS dependency referenced in config/assets, not a JS import; phantom-dep heuristic is a stable false positive here. ai
phantom-deps phantom-dep:@not-govuk/sass-base AI (phantom-deps): Same-org SASS base dependency; referenced in SCSS assets, not JS imports — stable false positive for this package. ai

Versions (showing 22 of 22)

Version Deps Published
0.18.1 6 / 8
0.18.0 6 / 8
0.17.4 6 / 8
0.17.3 6 / 8
0.17.2 6 / 8
0.17.1 6 / 8
0.17.0 6 / 8
0.16.3 6 / 9
0.16.2 6 / 9
0.16.1 6 / 9
0.16.0 6 / 9
0.15.14 6 / 8
0.15.12 6 / 8
0.15.11 6 / 8
0.15.10 6 / 8
0.15.9 6 / 8
0.15.8 6 / 8
0.15.7 6 / 8
0.15.6 6 / 8
0.15.5 6 / 8
0.15.4 6 / 8
0.15.3 6 / 8

v0.16.3

1 finding
LOW No provenance attestation provenance

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

v0.16.2

1 finding
LOW No provenance attestation provenance

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

v0.16.1

1 finding
LOW No provenance attestation provenance

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

v0.16.0

1 finding
LOW No provenance attestation provenance

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

v0.15.12

1 finding
LOW No provenance attestation provenance

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

v0.15.11

1 finding
LOW No provenance attestation provenance

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

v0.15.10

1 finding
LOW No provenance attestation provenance

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

v0.15.9

1 finding
LOW No provenance attestation provenance

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

v0.15.8

1 finding
LOW No provenance attestation provenance

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

v0.15.7

1 finding
LOW No provenance attestation provenance

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

v0.15.6

1 finding
LOW No provenance attestation provenance

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

v0.15.5

1 finding
LOW No provenance attestation provenance

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

v0.15.4

1 finding
LOW No provenance attestation provenance

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

v0.15.3

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.