← Home

@utrecht/calendar-react

npm Repository Homepage
24
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
dependencies unvetted-dep:@utrecht/calendar-css AI (dependencies): Same org/namespace as this package; published by the same trusted nl-design-system-ci publisher. ai
publish-pattern dormant-publish AI (publish-pattern): Published by GitHub Actions with SLSA provenance from the known nl-design-system org; dormancy likely reflects project cadence, not takeover. 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 24 of 24)

Version Deps Published
1.1.5 5 / 15
1.1.4 5 / 15
1.1.3 5 / 16
1.1.2 5 / 16
1.1.1 5 / 14
1.1.0 5 / 14
1.0.17 5 / 14
1.0.16 5 / 14
1.0.15 5 / 14
1.0.14 5 / 14
1.0.13 5 / 14
1.0.12 5 / 14
1.0.11 5 / 14
1.0.10 5 / 14
1.0.9 5 / 14
1.0.8 5 / 14
1.0.7 5 / 14
1.0.6 5 / 14
1.0.5 5 / 14
1.0.4 5 / 25
1.0.3 5 / 25
1.0.2 5 / 25
1.0.1 5 / 25
1.0.0 0 / 5

v1.1.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.11

1 finding
LOW No provenance attestation provenance

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

v1.0.10

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.

v1.0.9

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.

v1.0.8

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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