deps-sort
sort module-deps output for deterministic browserify bundles
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): goto-bus-stop is a well-established, highly trusted browserify ecosystem maintainer (1211 approved packages, 0 rejected). Publisher transition from zertosh is a known legitimate handoff. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects original author stepping back; the new publisher (goto-bus-stop) is a trusted ecosystem contributor, not an account takeover indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): shasum-object is a legitimate replacement for shasum in the browserify ecosystem, maintained by the same trusted contributor group. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 4 / 1 | |
| 2.0.0 | 4 / 1 | |
| 1.3.9 | 4 / 1 | |
| 1.3.8 | 5 / 1 | |
| 1.3.7 | 5 / 1 | |
| 1.3.6 | 5 / 1 | |
| 1.3.5 | 5 / 1 | |
| 1.3.4 | 5 / 1 | |
| 1.3.3 | 5 / 1 | |
| 1.3.2 | 5 / 1 | |
| 1.3.1 | 5 / 1 | |
| 1.3.0 | 5 / 1 | |
| 1.2.0 | 5 / 1 | |
| 1.1.0 | 4 / 1 | |
| 1.0.0 | 3 / 1 | |
| 0.1.2 | 3 / 1 | |
| 0.1.1 | 3 / 1 | |
| 0.1.0 | 3 / 1 | |
| 0.0.0 | 2 / 1 |
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2019-10-29. 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.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
2 findingsPackage 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 2015-04-26. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.