@digdir/designsystemet-theme
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Absolute size increase is 239B→1KB; trivially small and consistent with added CSS theme tokens, not injected payload. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established Norwegian gov design system; 158 versions published; dormancy likely reflects release cadence, not takeover. | ai | |
| dependencies | unvetted-dep:@digdir/designsystemet-types | AI (dependencies): Same-org monorepo sibling package; stable false positive for this package family. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.11.0 | 1 / 2 | |
| 1.10.0 | 1 / 2 | |
| 1.9.0 | 1 / 2 | |
| 1.8.0 | 1 / 2 | |
| 1.7.3 | 0 / 2 | |
| 1.7.2 | 0 / 2 | |
| 1.7.0 | 0 / 2 | |
| 1.4.0 | 0 / 2 | |
| 1.1.0 | 0 / 2 | |
| 1.0.8 | 0 / 2 | |
| 1.0.7 | 0 / 2 | |
| 1.0.6 | 0 / 1 | |
| 1.0.5 | 0 / 1 |
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.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mimarz.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mimarz.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mimarz.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
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.