← Home

@utrecht/textbox-react

15
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

littlebobbytabl.esyolijnnl-design-system-ci

Keywords

nl-design-system

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Consistent across all nl-design-system-ci published packages; not a risk indicator for this org. ai
license copyleft-license:EUPL-1.2 AI (license): EUPL-1.2 is the declared license for all Utrecht NL Design System packages; stable across versions. ai

Versions (showing 15 of 15)

Version Deps Published
1.0.16 2 / 15
1.0.15 2 / 15
1.0.14 2 / 15
1.0.13 2 / 13
1.0.12 2 / 13
1.0.11 2 / 13
1.0.10 2 / 13
1.0.9 2 / 13
1.0.8 2 / 13
1.0.7 2 / 13
1.0.6 2 / 13
1.0.5 2 / 13
1.0.4 1 / 14
1.0.3 1 / 14
1.0.0 1 / 26

v1.0.8

1 finding
INFO No provenance attestation provenance

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

v1.0.7

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.

v1.0.6

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.

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

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

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

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