@digdir/designsystemet-react
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@u-elements/u-tags | AI (dependencies): u-elements is a legitimate web components library used intentionally by this design system package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established design system package; missing keywords/README code blocks are cosmetic, not spam indicators. | ai | |
| dependencies | unvetted-dep:@digdir/designsystemet-web | AI (dependencies): First-party sibling package from same monorepo; not an independent risk. | ai | |
| dependencies | unvetted-dep:@digdir/designsystemet-types | AI (dependencies): First-party sibling package from same monorepo; not an independent risk. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 8 / 19 | |
| 1.14.0 | 8 / 19 | |
| 1.13.3 | 8 / 19 | |
| 1.13.2 | 8 / 19 | |
| 1.13.1 | 8 / 19 | |
| 1.13.0 | 8 / 19 | |
| 1.12.1 | 8 / 19 | |
| 1.12.0 | 8 / 19 | |
| 1.11.1 | 10 / 20 | |
| 1.11.0 | 10 / 20 | |
| 1.10.0 | 10 / 20 | |
| 1.9.0 | 10 / 21 | |
| 1.8.0 | 10 / 21 | |
| 1.7.3 | 9 / 21 | |
| 1.7.2 | 9 / 21 | |
| 1.6.1 | 9 / 21 | |
| 1.6.0 | 9 / 22 | |
| 1.5.1 | 9 / 22 | |
| 1.5.0 | 9 / 22 | |
| 1.4.0 | 9 / 22 | |
| 1.3.0 | 9 / 22 | |
| 1.2.0 | 9 / 22 | |
| 1.1.10 | 9 / 22 | |
| 1.1.9 | 9 / 22 | |
| 1.1.8 | 9 / 22 | |
| 1.1.7 | 9 / 22 | |
| 1.1.6 | 9 / 22 | |
| 1.1.5 | 9 / 21 | |
| 1.1.4 | 9 / 21 | |
| 1.1.3 | 9 / 21 | |
| 1.1.2 | 9 / 21 | |
| 1.1.1 | 9 / 21 | |
| 1.1.0 | 9 / 21 | |
| 1.0.6 | 9 / 23 | |
| 1.0.5 | 9 / 16 |
v1.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.