@diia-inhouse/validators
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:validator | AI (typosquat): Scoped @diia-inhouse package; established project with 33 versions and 690-day history, not a typosquat of 'validator'. | ai |
Versions (showing 51 of 86)
| Version | Deps | Published |
|---|---|---|
| 2.2.49 | 4 / 21 | |
| 2.2.48 | 4 / 21 | |
| 2.2.47 | 4 / 21 | |
| 2.2.46 | 4 / 21 | |
| 2.2.45 | 4 / 21 | |
| 2.2.44 | 4 / 21 | |
| 2.2.43 | 4 / 21 | |
| 2.2.41 | 4 / 21 | |
| 2.2.40 | 4 / 21 | |
| 2.2.39 | 4 / 21 | |
| 2.2.38 | 4 / 21 | |
| 2.2.37 | 4 / 21 | |
| 2.2.36 | 4 / 21 | |
| 2.2.35 | 4 / 21 | |
| 2.2.34 | 4 / 21 | |
| 2.2.33 | 4 / 21 | |
| 2.2.32 | 4 / 21 | |
| 2.2.31 | 4 / 21 | |
| 2.2.30 | 4 / 21 | |
| 2.2.29 | 4 / 21 | |
| 2.2.28 | 4 / 21 | |
| 2.2.27 | 4 / 21 | |
| 2.2.26 | 4 / 21 | |
| 2.2.25 | 4 / 21 | |
| 2.2.24 | 4 / 21 | |
| 2.2.23 | 4 / 21 | |
| 2.2.22 | 4 / 21 | |
| 2.2.21 | 4 / 21 | |
| 2.2.20 | 4 / 21 | |
| 2.2.19 | 4 / 21 | |
| 2.2.18 | 4 / 21 | |
| 2.2.17 | 4 / 21 | |
| 2.2.16 | 4 / 21 | |
| 2.2.15 | 4 / 21 | |
| 2.2.14 | 4 / 21 | |
| 2.2.13 | 4 / 21 | |
| 2.2.12 | 4 / 21 | |
| 2.2.11 | 4 / 21 | |
| 2.2.10 | 4 / 21 | |
| 2.2.9 | 4 / 21 | |
| 2.2.8 | 4 / 21 | |
| 2.2.7 | 4 / 21 | |
| 2.2.6 | 4 / 21 | |
| 2.2.5 | 4 / 21 | |
| 2.2.4 | 4 / 21 | |
| 2.2.3 | 4 / 21 | |
| 2.2.2 | 4 / 21 | |
| 2.2.1 | 4 / 21 | |
| 2.2.0 | 4 / 21 | |
| 1.28.36 | 4 / 18 | |
| 1.28.35 | 4 / 18 |
v2.2.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.