@wisemen/validators
Supply chain provenance
Status for the latest visible version.
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 @wisemen org package; not impersonating 'validator', just a validators utility from the same org. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.0.23 | 1 / 4 | |
| 0.0.22 | 1 / 4 | |
| 0.0.21 | 0 / 2 | |
| 0.0.20 | 0 / 2 | |
| 0.0.19 | 0 / 1 | |
| 0.0.18 | 0 / 1 | |
| 0.0.17 | 0 / 1 | |
| 0.0.16 | 0 / 1 | |
| 0.0.15 | 0 / 1 | |
| 0.0.14 | 3 / 1 | |
| 0.0.13 | 3 / 1 |
v0.0.23
2 findingsPackage name '@wisemen/validators' is 1 edit(s) away from popular package 'validator'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.22
2 findingsPackage name '@wisemen/validators' is 1 edit(s) away from popular package 'validator'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.21
2 findingsPackage name '@wisemen/validators' is 1 edit(s) away from popular package 'validator'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
2 findingsPackage name '@wisemen/validators' is 1 edit(s) away from popular package 'validator'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
2 findingsPackage name '@wisemen/validators' is 1 edit(s) away from popular package 'validator'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
2 findingsPackage name '@wisemen/validators' is 1 edit(s) away from popular package 'validator'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
2 findingsPackage name '@wisemen/validators' is 1 edit(s) away from popular package 'validator'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
2 findingsPackage name '@wisemen/validators' is 1 edit(s) away from popular package 'validator'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
2 findingsPackage name '@wisemen/validators' is 1 edit(s) away from popular package 'validator'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
2 findingsPackage name '@wisemen/validators' is 1 edit(s) away from popular package 'validator'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.