du
A simple JavaScript implementation of `du -sb`
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 from rvagg to timoxley occurred in 2013 — a well-documented, legitimate maintainer transition between two established Node.js ecosystem contributors. Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): timoxley is a long-standing npm publisher with a strong track record. This addition reflects the same 2013 legitimate handoff and is not a risk signal for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): 'du' is the Unix disk-usage command this package implements, not a typosquat of 'pg'. Short name collision is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): 'du' is the Unix disk-usage command this package implements, not a typosquat of 'qs'. Short name collision is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): 'du' is the Unix disk-usage command this package implements, not a typosquat of 'yup'. Short name collision is coincidental. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is the legitimate initial version of this 4880-day-old package by a highly trusted publisher (rvagg). Not indicative of malicious intent. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 1 / 1 | |
| 0.1.1 | 1 / 1 | |
| 0.1.0 | 1 / 1 | |
| 0.0.2 | 1 / 1 | |
| 0.0.1 | 1 / 1 | |
| 0.0.0 | 1 / 1 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
2 findingsThis version was published by a different npm account than previous versions on 2013-06-18. 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.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.