← Home

@not-govuk/notification-banner

A component to tell the user about something they need to know about, but that’s not directly related to the page content.

18
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
provenance no-provenance AI (provenance): Established package with clean history; lack of provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:govuk-frontend AI (phantom-deps): Referenced in SCSS/config files, not JS imports; stable pattern for this GOV.UK component package. ai
phantom-deps phantom-dep:@not-govuk/sass-base AI (phantom-deps): Same-org SCSS dependency; referenced in stylesheet assets, not JS imports. Stable for this package. ai

Versions (showing 18 of 18)

Version Deps Published
0.18.1 3 / 7
0.18.0 3 / 7
0.17.4 3 / 7
0.17.3 3 / 7
0.17.2 3 / 7
0.17.1 3 / 7
0.17.0 3 / 7
0.16.2 3 / 8
0.16.1 3 / 8
0.15.14 3 / 8
0.15.13 3 / 8
0.8.6 3 / 8
0.8.5 3 / 8
0.8.4 3 / 8
0.8.3 3 / 8
0.8.2 3 / 8
0.8.1 3 / 8
0.8.0 3 / 8

v0.8.6

1 finding
INFO No provenance attestation provenance

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

v0.8.5

1 finding
INFO No provenance attestation provenance

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

v0.8.4

1 finding
INFO No provenance attestation provenance

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

v0.8.3

1 finding
INFO No provenance attestation provenance

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

v0.8.2

1 finding
INFO No provenance attestation provenance

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

v0.8.1

1 finding
INFO No provenance attestation provenance

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

v0.8.0

1 finding
INFO No provenance attestation provenance

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