@hg-ts/validation
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@nestjs/common | AI (phantom-deps): NestJS peer dep; expected to be declared but not directly imported in a validation library. | ai | |
| phantom-deps | phantom-dep:@nestjs/swagger | AI (phantom-deps): NestJS Swagger peer dep; declared for typing/integration, not directly imported. | ai | |
| phantom-deps | phantom-dep:openapi3-ts | AI (phantom-deps): openapi3-ts is a transitive type dependency of @anatine/zod-openapi; phantom-dep is a stable false positive here. | ai | |
| typosquat | typosquat.levenshtein:validator | AI (typosquat): Scoped @hg-ts monorepo package; name reflects its validation purpose, not an impersonation of 'validator'. | ai |
Versions (showing 100 of 206)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 3 / 10 | |
| 0.2.2 | 3 / 10 | |
| 0.2.1 | 3 / 10 | |
| 0.2.0 | 3 / 10 | |
| 0.1.117 | 3 / 10 | |
| 0.1.116 | 3 / 10 | |
| 0.1.115 | 3 / 10 | |
| 0.1.114 | 3 / 10 | |
| 0.1.112 | 3 / 10 | |
| 0.1.111 | 3 / 10 | |
| 0.1.110 | 3 / 10 | |
| 0.1.109 | 3 / 10 | |
| 0.1.108 | 3 / 10 | |
| 0.1.107 | 3 / 10 | |
| 0.1.106 | 3 / 10 | |
| 0.1.105 | 3 / 10 | |
| 0.1.104 | 3 / 10 | |
| 0.1.103 | 3 / 10 | |
| 0.1.102 | 3 / 10 | |
| 0.1.101 | 3 / 10 | |
| 0.1.100 | 3 / 10 | |
| 0.1.99 | 3 / 10 | |
| 0.1.98 | 3 / 10 | |
| 0.1.97 | 3 / 10 | |
| 0.1.96 | 3 / 10 | |
| 0.1.95 | 3 / 10 | |
| 0.1.94 | 3 / 10 | |
| 0.1.93 | 3 / 10 | |
| 0.1.92 | 3 / 10 | |
| 0.1.91 | 3 / 10 | |
| 0.1.90 | 3 / 10 | |
| 0.1.89 | 3 / 10 | |
| 0.1.88 | 3 / 10 | |
| 0.1.87 | 3 / 10 | |
| 0.1.86 | 3 / 10 | |
| 0.1.85 | 3 / 10 | |
| 0.1.84 | 3 / 10 | |
| 0.1.83 | 3 / 10 | |
| 0.1.82 | 3 / 10 | |
| 0.1.81 | 3 / 10 | |
| 0.1.80 | 3 / 10 | |
| 0.1.79 | 3 / 10 | |
| 0.1.78 | 3 / 10 | |
| 0.1.77 | 3 / 10 | |
| 0.1.76 | 3 / 10 | |
| 0.1.75 | 3 / 10 | |
| 0.1.74 | 3 / 10 | |
| 0.1.73 | 3 / 10 | |
| 0.1.72 | 3 / 10 | |
| 0.1.71 | 3 / 10 | |
| 0.1.70 | 3 / 10 | |
| 0.1.69 | 3 / 10 | |
| 0.1.68 | 3 / 10 | |
| 0.1.67 | 3 / 10 | |
| 0.1.66 | 3 / 10 | |
| 0.1.65 | 6 / 11 | |
| 0.1.64 | 2 / 10 | |
| 0.1.63 | 2 / 10 | |
| 0.1.62 | 2 / 10 | |
| 0.1.61 | 2 / 10 | |
| 0.1.60 | 2 / 10 | |
| 0.1.59 | 2 / 10 | |
| 0.1.58 | 2 / 10 | |
| 0.1.57 | 1 / 9 | |
| 0.1.56 | 1 / 9 | |
| 0.1.55 | 1 / 9 | |
| 0.1.54 | 1 / 9 | |
| 0.1.53 | 1 / 9 | |
| 0.1.52 | 1 / 9 | |
| 0.1.51 | 1 / 9 | |
| 0.1.50 | 2 / 12 | |
| 0.1.49 | 2 / 12 | |
| 0.1.48 | 2 / 12 | |
| 0.1.47 | 2 / 12 | |
| 0.1.46 | 2 / 12 | |
| 0.1.45 | 2 / 12 | |
| 0.1.44 | 2 / 12 | |
| 0.1.43 | 2 / 12 | |
| 0.1.42 | 2 / 12 | |
| 0.1.41 | 2 / 12 | |
| 0.1.40 | 1 / 12 | |
| 0.1.39 | 1 / 12 | |
| 0.1.38 | 1 / 12 | |
| 0.1.37 | 1 / 12 | |
| 0.1.36 | 1 / 12 | |
| 0.1.35 | 1 / 12 | |
| 0.1.34 | 1 / 12 | |
| 0.1.33 | 1 / 12 | |
| 0.1.32 | 1 / 12 | |
| 0.1.31 | 1 / 12 | |
| 0.1.29 | 1 / 12 | |
| 0.1.28 | 1 / 12 | |
| 0.1.27 | 1 / 12 | |
| 0.1.26 | 1 / 12 | |
| 0.1.25 | 1 / 12 | |
| 0.1.24 | 1 / 12 | |
| 0.1.23 | 1 / 12 | |
| 0.1.22 | 1 / 12 | |
| 0.1.21 | 1 / 12 | |
| 0.1.20 | 1 / 12 |
v0.1.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.