@diia-inhouse/design-system
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a TypeScript types package; it is not directly imported in code but is legitimately declared as a dependency for type resolution. Stable false positive for this package. | ai |
Versions (showing 51 of 76)
| Version | Deps | Published |
|---|---|---|
| 4.7.1 | 1 / 13 | |
| 4.7.0 | 1 / 13 | |
| 4.6.1 | 1 / 13 | |
| 4.6.0 | 1 / 13 | |
| 4.5.0 | 1 / 13 | |
| 4.4.0 | 1 / 13 | |
| 4.3.0 | 1 / 13 | |
| 4.1.0 | 1 / 13 | |
| 4.0.6 | 1 / 13 | |
| 4.0.5 | 1 / 13 | |
| 4.0.4 | 1 / 13 | |
| 4.0.3 | 1 / 14 | |
| 4.0.2 | 1 / 14 | |
| 4.0.1 | 1 / 14 | |
| 3.29.0 | 1 / 11 | |
| 3.28.1 | 1 / 11 | |
| 3.28.0 | 1 / 11 | |
| 3.27.3 | 1 / 11 | |
| 3.27.2 | 1 / 11 | |
| 3.27.1 | 1 / 11 | |
| 3.27.0 | 1 / 11 | |
| 3.26.1 | 1 / 11 | |
| 3.26.0 | 1 / 11 | |
| 3.25.0 | 1 / 11 | |
| 3.24.0 | 1 / 11 | |
| 3.23.0 | 1 / 11 | |
| 3.22.0 | 1 / 11 | |
| 3.21.1 | 1 / 11 | |
| 3.21.0 | 1 / 11 | |
| 3.20.2 | 1 / 11 | |
| 3.20.1 | 1 / 11 | |
| 3.20.0 | 1 / 11 | |
| 3.19.0 | 1 / 11 | |
| 3.18.2 | 1 / 11 | |
| 3.18.1 | 1 / 11 | |
| 3.18.0 | 1 / 11 | |
| 3.17.4 | 1 / 11 | |
| 3.17.3 | 1 / 11 | |
| 3.17.2 | 1 / 11 | |
| 3.17.1 | 1 / 11 | |
| 3.17.0 | 1 / 11 | |
| 3.16.1 | 1 / 11 | |
| 3.16.0 | 1 / 11 | |
| 3.15.0 | 1 / 11 | |
| 3.14.0 | 1 / 11 | |
| 3.13.0 | 1 / 11 | |
| 3.12.0 | 1 / 11 | |
| 3.11.0 | 1 / 11 | |
| 3.10.0 | 1 / 11 | |
| 3.9.2 | 1 / 11 | |
| 3.9.1 | 1 / 11 |
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.