@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 21 of 21)
| 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 | |
| 0.0.12 | 3 / 1 | |
| 0.0.11 | 3 / 1 | |
| 0.0.10 | 3 / 1 | |
| 0.0.9 | 3 / 1 | |
| 0.0.8 | 3 / 1 | |
| 0.0.7 | 3 / 1 | |
| 0.0.6 | 3 / 1 | |
| 0.0.5 | 3 / 1 | |
| 0.0.4 | 3 / 1 | |
| 0.0.3 | 3 / 1 |
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kobe-kwanten-wisemen) than the most recent previously approved version (jorenvandeweyer) on 2025-04-24, but kobe-kwanten-wisemen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kobe-kwanten-wisemen) than the most recent previously approved version (jorenvandeweyer) on 2025-04-24, but kobe-kwanten-wisemen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jorenvandeweyer) than the most recent previously approved version (kobe-kwanten-wisemen) on 2025-04-11, but jorenvandeweyer is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kobe-kwanten-wisemen) than the most recent previously approved version (jorenvandeweyer) on 2025-04-06, but kobe-kwanten-wisemen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kobe-kwanten-wisemen) than the most recent previously approved version (jorenvandeweyer) on 2025-04-06, but kobe-kwanten-wisemen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.