class-validator
Decorator-based property validation for classes.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/validator | AI (phantom-deps): @types/* packages are consumed by TypeScript at compile time and are not directly imported in source; phantom-dep firing on them is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): class-validator is an established TypeStack package with a known GitHub repo; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.15.1 | 3 / 0 | |
| 0.14.4 | 3 / 0 | |
| 0.14.3 | 3 / 0 | |
| 0.14.2 | 3 / 0 | |
| 0.14.1 | 3 / 0 | |
| 0.14.0 | 3 / 0 |
v0.15.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.
v0.14.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.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.
v0.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.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.
v0.14.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.