@diia-inhouse/env
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @diia-inhouse/env is part of the legitimate Diia open-source ecosystem; Levenshtein comparison to 'ajv' is a false positive for scoped packages in this namespace. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 3.3.7 | 3 / 19 | |
| 3.3.6 | 3 / 19 | |
| 3.3.5 | 3 / 19 | |
| 3.3.4 | 3 / 19 | |
| 3.3.3 | 3 / 19 | |
| 3.3.2 | 3 / 19 | |
| 3.3.1 | 3 / 19 | |
| 3.3.0 | 3 / 19 | |
| 2.8.25 | 3 / 16 | |
| 2.8.24 | 3 / 16 | |
| 2.8.22 | 3 / 16 | |
| 2.8.21 | 3 / 16 | |
| 2.8.20 | 3 / 16 | |
| 2.8.19 | 3 / 16 | |
| 2.8.18 | 3 / 16 | |
| 2.8.17 | 3 / 16 | |
| 2.8.16 | 3 / 16 | |
| 2.8.15 | 3 / 16 | |
| 2.8.14 | 3 / 16 | |
| 2.8.13 | 3 / 16 | |
| 2.8.12 | 3 / 16 | |
| 2.8.11 | 3 / 16 | |
| 2.8.10 | 3 / 16 | |
| 2.8.9 | 3 / 16 | |
| 2.8.8 | 3 / 16 | |
| 2.8.7 | 3 / 16 | |
| 2.8.6 | 3 / 16 | |
| 2.8.5 | 3 / 16 | |
| 2.8.4 | 3 / 16 | |
| 2.8.3 | 3 / 16 | |
| 2.8.2 | 3 / 16 | |
| 2.8.1 | 3 / 16 | |
| 2.8.0 | 4 / 17 |
v3.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.