@open-formulieren/design-tokens
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.68.1 | 0 / 4 | |
| 0.68.0 | 0 / 4 | |
| 0.67.0 | 0 / 4 | |
| 0.66.0 | 0 / 4 | |
| 0.65.0 | 0 / 4 | |
| 0.64.0 | 0 / 4 | |
| 0.63.0 | 0 / 4 | |
| 0.62.0 | 0 / 4 | |
| 0.61.0 | 0 / 4 | |
| 0.60.1 | 0 / 4 | |
| 0.60.0 | 0 / 4 | |
| 0.59.1 | 0 / 4 | |
| 0.59.0 | 0 / 4 | |
| 0.58.0 | 0 / 4 | |
| 0.57.0 | 0 / 4 | |
| 0.56.1 | 0 / 4 | |
| 0.56.0 | 0 / 4 | |
| 0.55.0 | 0 / 4 | |
| 0.54.0 | 0 / 4 | |
| 0.53.0 | 0 / 4 |
v0.68.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.68.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.59.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.