@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, so a manually published version cannot be tied back to a reviewed commit.
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 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 3.3.39 | 3 / 19 | |
| 3.3.38 | 3 / 19 | |
| 3.3.37 | 3 / 19 | |
| 3.3.36 | 3 / 19 | |
| 3.3.35 | 3 / 19 | |
| 3.3.34 | 3 / 19 | |
| 3.3.33 | 3 / 19 | |
| 3.3.32 | 3 / 19 | |
| 3.3.31 | 3 / 19 | |
| 3.3.30 | 3 / 19 | |
| 3.3.29 | 3 / 19 | |
| 3.3.28 | 3 / 19 | |
| 3.3.27 | 3 / 19 | |
| 3.3.26 | 3 / 19 | |
| 3.3.25 | 3 / 19 | |
| 3.3.24 | 3 / 19 | |
| 3.3.23 | 3 / 19 | |
| 3.3.22 | 3 / 19 | |
| 3.3.21 | 3 / 19 | |
| 3.3.20 | 3 / 19 | |
| 3.3.19 | 3 / 19 | |
| 3.3.18 | 3 / 19 | |
| 3.3.17 | 3 / 19 | |
| 3.3.16 | 3 / 19 | |
| 3.3.15 | 3 / 19 | |
| 3.3.14 | 3 / 19 | |
| 3.3.12 | 3 / 19 | |
| 3.3.11 | 3 / 19 | |
| 3.3.10 | 3 / 19 | |
| 3.3.9 | 3 / 19 | |
| 3.3.8 | 3 / 19 | |
| 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 |
v3.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.