module-deps
walk the dependency graph to generate json output that can be fed into browser-pack
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): Legitimate maintainer transition from substack to goto-bus-stop within the browserify org, occurred in 2018. goto-bus-stop is a trusted maintainer. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; low-severity informational finding for a well-established ecosystem package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): module-deps is a dependency resolver that intentionally uses dynamic require() to load transform modules — this is core, documented functionality present across all versions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): ljharb stepping back from maintainership is a known pattern across many packages; current publisher goto-bus-stop is a legitimate long-standing browserify contributor with a strong track record. | ai |
Versions (showing 51 of 139)
| Version | Deps | Published |
|---|---|---|
| 6.2.3 | 15 / 2 | |
| 6.2.2 | 15 / 2 | |
| 6.2.1 | 15 / 2 | |
| 6.2.0 | 15 / 2 | |
| 6.1.0 | 15 / 2 | |
| 6.0.2 | 15 / 2 | |
| 6.0.1 | 15 / 2 | |
| 6.0.0 | 15 / 2 | |
| 5.0.1 | 15 / 2 | |
| 5.0.0 | 15 / 2 | |
| 4.1.1 | 15 / 2 | |
| 4.1.0 | 15 / 2 | |
| 4.0.8 | 15 / 2 | |
| 4.0.7 | 14 / 2 | |
| 4.0.6 | 14 / 2 | |
| 4.0.5 | 14 / 2 | |
| 4.0.4 | 14 / 2 | |
| 4.0.3 | 14 / 2 | |
| 4.0.2 | 14 / 2 | |
| 4.0.1 | 14 / 2 | |
| 4.0.0 | 14 / 2 | |
| 3.9.1 | 14 / 2 | |
| 3.9.0 | 14 / 2 | |
| 3.8.1 | 14 / 2 | |
| 3.8.0 | 14 / 2 | |
| 3.7.13 | 14 / 3 | |
| 3.7.12 | 15 / 3 | |
| 3.7.11 | 15 / 3 | |
| 3.7.10 | 15 / 3 | |
| 3.7.8 | 15 / 3 | |
| 3.7.7 | 16 / 3 | |
| 3.7.6 | 16 / 3 | |
| 3.7.5 | 16 / 3 | |
| 3.7.4 | 15 / 3 | |
| 3.7.3 | 15 / 3 | |
| 3.7.2 | 15 / 3 | |
| 3.7.1 | 14 / 3 | |
| 3.7.0 | 14 / 3 | |
| 3.6.5 | 14 / 3 | |
| 3.6.4 | 14 / 3 | |
| 3.6.3 | 14 / 3 | |
| 3.6.2 | 14 / 3 | |
| 3.6.1 | 14 / 3 | |
| 3.6.0 | 14 / 3 | |
| 3.5.12 | 14 / 3 | |
| 3.5.11 | 14 / 3 | |
| 3.5.10 | 14 / 3 | |
| 3.5.9 | 14 / 3 | |
| 3.5.8 | 14 / 3 | |
| 3.5.7 | 14 / 3 | |
| 3.5.6 | 14 / 3 |
v6.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
2 findingsThis version was published by a different npm account than previous versions on 2018-03-28. 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.
v6.0.1
2 findingsThis version was published by a different npm account than previous versions on 2018-03-26. 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.
v6.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-02-07. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-01-06. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-01-02. This could indicate a legitimate maintainer transition or an account compromise.