list-methods
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:test/fixtures/lodash.js | AI (source-diff): test/fixtures/lodash.js is the canonical Lo-Dash 2.4.1 source included as a test fixture. The net-exec detection is a false positive on lodash's standard IIFE and Function usage. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is entirely due to adding the lodash 2.4.1 source as a test fixture (~240KB). No injected payload. | ai | |
| phantom-deps | phantom-dep:prompt | AI (phantom-deps): prompt is a legitimate declared dependency used via config files, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:globule | AI (phantom-deps): globule is a legitimate declared dependency used via config files, not a security concern for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is the core feature of this CLI tool — it loads user-specified modules to list their methods. Not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates npm Sigstore provenance by years; absence is expected and not a risk signal for this publisher. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.3.3 | 7 / 3 | |
| 0.3.2 | 6 / 3 | |
| 0.3.1 | 6 / 1 | |
| 0.3.0 | 6 / 1 | |
| 0.2.7 | 6 / 0 | |
| 0.2.6 | 6 / 0 | |
| 0.2.5 | 6 / 0 | |
| 0.2.4 | 6 / 0 | |
| 0.2.3 | 6 / 0 | |
| 0.2.2 | 6 / 0 | |
| 0.2.1 | 6 / 0 | |
| 0.2.0 | 6 / 0 | |
| 0.1.0 | 4 / 0 |
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.