util
Node.js's util module for all engines
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change reflects legitimate transfer to defunctzombie/goto-bus-stop; repo URL in package.json matches defunctzombie's GitHub account, confirming ownership. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers defunctzombie and goto-bus-stop are the canonical owners; repo URL confirms defunctzombie's ownership of this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): shtylman removal is consistent with a legitimate ownership transfer to defunctzombie, who owns the referenced GitHub repository. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): inherits is a well-known, widely-trusted npm package; its addition as a runtime dep for a Node.js util polyfill is benign. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage is a direct port of Node.js util.exec(), consistent with this package's purpose of providing Node core module APIs. Not malicious. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): 'util' is a legitimate, long-standing Node.js polyfill package with no relation to 'uuid'; the Levenshtein match is a stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.12.5 | 5 / 8 | |
| 0.12.4 | 6 / 7 | |
| 0.12.3 | 6 / 7 | |
| 0.12.2 | 4 / 6 | |
| 0.12.1 | 5 / 5 | |
| 0.12.0 | 5 / 4 | |
| 0.11.1 | 1 / 4 | |
| 0.11.0 | 1 / 4 | |
| 0.10.4 | 1 / 1 | |
| 0.10.3 | 1 / 1 | |
| 0.10.2 | 1 / 1 | |
| 0.10.1 | 1 / 1 | |
| 0.10.0 | 0 / 1 | |
| 0.4.9 | 1 / 0 |
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
2 findingsThis version was published by a different npm account than previous versions on 2019-05-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
2 findingsThis version was published by a different npm account than previous versions on 2018-11-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findingsThis version was published by a different npm account than previous versions on 2018-06-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
2 findingsThis version was published by a different npm account than previous versions on 2018-06-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.