@diia-inhouse/utils
Generic utils
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:design-system | AI (dependencies): design-system is a phantom dep in this package (not directly imported, only referenced in config files). Low runtime risk for this package context. | ai | |
| provenance | no-provenance | AI (provenance): Diia open-source packages consistently publish without Sigstore provenance; this is a stable characteristic of the publisher, not a security concern. | ai | |
| dependencies | unvetted-dep:fast-levenshtein | AI (dependencies): fast-levenshtein is a well-known, widely-used string distance library with no known security issues; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/luxon | AI (phantom-deps): Framework-scoped type package; phantom dep finding is expected for type-only packages loaded by convention. | ai | |
| phantom-deps | phantom-dep:bson | AI (phantom-deps): bson is a well-known MongoDB BSON library; phantom dep finding reflects a code quality issue (unused dep), not a security risk. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): Standard license declaration pattern for custom/institutional licenses; common in government open-source projects like Diia. | ai | |
| phantom-deps | phantom-dep:design-system | AI (phantom-deps): Part of the Diia ecosystem; phantom dep finding reflects config-only reference, not a security concern. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): moment is a well-known date library; phantom dep finding reflects unused dependency, not a security concern. | ai | |
| phantom-deps | phantom-dep:type-fest | AI (phantom-deps): type-fest is a well-known TypeScript utility types library; phantom dep finding is a code quality issue, not a security risk. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 6.0.18 | 10 / 23 | |
| 6.0.17 | 10 / 23 | |
| 6.0.16 | 10 / 23 | |
| 6.0.15 | 10 / 23 | |
| 6.0.14 | 10 / 23 | |
| 6.0.13 | 10 / 23 | |
| 6.0.12 | 10 / 23 | |
| 6.0.11 | 10 / 23 | |
| 6.0.10 | 10 / 23 | |
| 6.0.9 | 10 / 23 | |
| 6.0.8 | 10 / 23 | |
| 5.3.30 | 11 / 20 | |
| 5.3.29 | 11 / 20 | |
| 5.3.28 | 11 / 20 | |
| 5.3.25 | 11 / 20 | |
| 5.3.24 | 11 / 20 | |
| 5.3.23 | 11 / 20 | |
| 5.3.22 | 11 / 20 | |
| 5.3.21 | 11 / 20 | |
| 5.3.20 | 11 / 20 | |
| 5.3.19 | 11 / 20 | |
| 5.3.18 | 11 / 20 | |
| 5.3.17 | 11 / 20 | |
| 5.3.16 | 11 / 20 | |
| 5.3.15 | 11 / 20 | |
| 5.3.14 | 11 / 20 | |
| 5.3.13 | 11 / 20 | |
| 5.3.12 | 11 / 20 | |
| 5.3.11 | 11 / 20 | |
| 5.3.10 | 11 / 20 | |
| 5.3.9 | 11 / 20 | |
| 5.3.8 | 11 / 20 | |
| 5.3.7 | 11 / 20 | |
| 5.3.6 | 11 / 20 | |
| 5.3.5 | 11 / 20 | |
| 5.3.4 | 11 / 20 | |
| 5.3.3 | 11 / 20 | |
| 5.3.2 | 11 / 20 | |
| 5.3.1 | 11 / 20 | |
| 5.3.0 | 11 / 20 |
v6.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.