@wisemen/time
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:vite | AI (typosquat): Scoped @wisemen package; name similarity to vite is coincidental, not impersonation. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.0.32 | 0 / 7 | |
| 0.0.31 | 0 / 7 | |
| 0.0.30 | 0 / 7 | |
| 0.0.29 | 0 / 7 | |
| 0.0.28 | 0 / 7 | |
| 0.0.27 | 0 / 7 | |
| 0.0.26 | 0 / 7 | |
| 0.0.25 | 0 / 7 | |
| 0.0.24 | 2 / 7 | |
| 0.0.23 | 2 / 7 | |
| 0.0.22 | 2 / 7 | |
| 0.0.21 | 2 / 8 | |
| 0.0.20 | 2 / 8 | |
| 0.0.19 | 2 / 8 | |
| 0.0.18 | 2 / 3 | |
| 0.0.17 | 1 / 3 |
v0.0.21
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 (jonasvannieuwenhuijsen) 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.20
2 findingsThis version was published by a different npm account (jonasvannieuwenhuijsen) than the most recent previously approved version (kobe-kwanten-wisemen) on 2025-03-07. It has since remained available on npm for 498 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
2 findingsThis version was published by a different npm account (jonasvannieuwenhuijsen) than the most recent previously approved version (kobe-kwanten-wisemen) on 2025-03-06. It has since remained available on npm for 499 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.