← Home

@not-govuk/error-message

npm

An error message associated with a form field.

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.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Consistent across all versions of this org's packages; not a per-version risk signal. ai
phantom-deps phantom-dep:govuk-frontend AI (phantom-deps): govuk-frontend is referenced in SCSS/config assets, not JS imports; phantom-dep heuristic is a stable false positive here. ai
phantom-deps phantom-dep:@not-govuk/sass-base AI (phantom-deps): Same-org SCSS dependency; not imported in JS but used in SCSS assets — stable false positive. ai

Versions (showing 10 of 10)

Version Deps Published
0.18.1 4 / 6
0.18.0 4 / 6
0.17.4 4 / 6
0.17.3 4 / 6
0.17.2 4 / 6
0.17.1 4 / 6
0.17.0 4 / 6
0.16.3 4 / 7
0.16.1 4 / 7
0.15.14 4 / 7

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

v0.16.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.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.