@db-ux/core-components
General technical components (styling, fonts and icons) out of DB UX Design System (Version 3)
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation; legitimate automation change for this org. | ai | |
| provenance | missing-githead | AI (provenance): CI/CD pipeline change explains missing gitHead; SLSA attestation provides equivalent provenance. | ai | |
| phantom-deps | phantom-dep:@db-ux/core-foundations | AI (phantom-deps): Same-org sibling package; used via CSS/asset pipeline rather than direct JS import. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 5.0.2 | 1 / 16 | |
| 5.0.1 | 1 / 16 | |
| 5.0.0 | 1 / 16 | |
| 4.14.0 | 1 / 16 | |
| 4.13.0 | 1 / 16 | |
| 4.12.1 | 1 / 16 | |
| 4.12.0 | 1 / 16 | |
| 4.11.1 | 1 / 16 | |
| 4.11.0 | 1 / 16 | |
| 4.10.2 | 1 / 16 | |
| 4.10.1 | 1 / 16 | |
| 4.10.0 | 1 / 16 | |
| 4.9.1 | 1 / 16 | |
| 4.9.0 | 1 / 16 | |
| 4.8.0 | 1 / 16 | |
| 4.7.3 | 1 / 16 | |
| 4.7.2 | 1 / 14 | |
| 4.7.1 | 1 / 14 | |
| 4.7.0 | 1 / 14 | |
| 4.6.1 | 1 / 14 | |
| 4.6.0 | 1 / 14 | |
| 4.5.4 | 1 / 14 | |
| 4.5.3 | 1 / 14 | |
| 4.5.2 | 1 / 14 | |
| 4.5.1 | 1 / 14 | |
| 4.5.0 | 1 / 13 | |
| 4.4.3 | 1 / 13 | |
| 4.4.2 | 1 / 12 | |
| 4.4.1 | 1 / 12 | |
| 4.4.0 | 1 / 12 | |
| 4.3.2 | 1 / 12 | |
| 4.3.1 | 1 / 12 | |
| 4.3.0 | 1 / 12 | |
| 4.2.6 | 1 / 11 | |
| 4.2.5 | 1 / 11 | |
| 4.2.4 | 1 / 11 | |
| 4.2.3 | 1 / 11 | |
| 4.2.2 | 1 / 11 | |
| 4.2.1 | 1 / 11 | |
| 4.2.0 | 1 / 11 |
v5.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.4
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v4.5.3
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v4.5.2
3 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (mfranzke) on 2026-03-04, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v4.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.