complexity-report
Software complexity analysis for JavaScript projects
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): The addisonj → philbooth transition occurred in 2015 and philbooth is the documented author. This is a historical legitimate maintainer transfer, not a compromise. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load user-specified output format plugins via CLI argument — standard and expected behavior for this tool. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 6 / 3 | |
| 1.4.0 | 6 / 3 | |
| 1.3.1 | 5 / 3 | |
| 1.3.0 | 5 / 3 | |
| 1.2.0 | 3 / 3 | |
| 1.1.1 | 3 / 3 | |
| 1.1.0 | 3 / 3 | |
| 1.0.7 | 3 / 3 | |
| 1.0.6 | 3 / 3 | |
| 1.0.5 | 3 / 3 | |
| 1.0.4 | 3 / 3 | |
| 1.0.3 | 3 / 3 | |
| 1.0.2 | 3 / 3 | |
| 1.0.1 | 3 / 3 | |
| 1.0.0 | 3 / 3 | |
| 0.10.5 | 3 / 4 | |
| 0.10.4 | 3 / 4 | |
| 0.10.3 | 3 / 4 | |
| 0.10.2 | 3 / 4 | |
| 0.10.1 | 3 / 4 | |
| 0.9.1 | 3 / 4 | |
| 0.9.0 | 3 / 4 | |
| 0.8.1 | 3 / 4 | |
| 0.8.0 | 3 / 4 | |
| 0.7.0 | 3 / 4 | |
| 0.6.2 | 3 / 4 | |
| 0.6.1 | 3 / 4 | |
| 0.6.0 | 3 / 4 | |
| 0.5.2 | 3 / 4 | |
| 0.5.1 | 3 / 4 | |
| 0.5.0 | 3 / 4 | |
| 0.4.3 | 3 / 4 | |
| 0.4.2 | 3 / 4 | |
| 0.4.1 | 3 / 4 | |
| 0.4.0 | 3 / 4 | |
| 0.3.0 | 3 / 4 | |
| 0.2.8 | 3 / 4 | |
| 0.2.7 | 3 / 4 | |
| 0.2.6 | 3 / 4 | |
| 0.2.5 | 3 / 4 | |
| 0.2.4 | 3 / 5 | |
| 0.2.3 | 3 / 5 | |
| 0.2.2 | 3 / 5 | |
| 0.2.1 | 4 / 5 | |
| 0.2.0 | 4 / 5 | |
| 0.1.5 | 4 / 5 | |
| 0.1.4 | 4 / 5 | |
| 0.1.3 | 3 / 5 | |
| 0.1.2 | 3 / 5 | |
| 0.1.1 | 3 / 5 | |
| 0.1.0 | 3 / 5 |
v1.4.1
2 findingsThis version was published by a different npm account than previous versions on 2015-06-22. 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.
v1.4.0
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
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-02-23. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
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.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
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.