@oclif/plugin-test-esbuild
Bundled plugin for testing
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:dist/chunk-LPEKLRLJ.js | AI (source-diff): esbuild bundle of @oclif/core; __commonJS shims trigger heuristic but contain no actual network/exec payload. | ai | |
| source-diff | net-exec-file:dist/chunk-DQZ52UMY.js | AI (source-diff): Large esbuild bundle of @oclif/core deps; network+exec pattern is from bundled library code, not malware. | ai | |
| source-diff | net-exec-file:dist/chunk-EKTKY2AC.js | AI (source-diff): Large esbuild bundle of @oclif/core; network+exec pattern is from bundled oclif internals, not malware. | ai | |
| source-diff | net-exec-file:dist/chunk-HPGMPWKK.js | AI (source-diff): esbuild bundle of oclif/core deps; network+exec pattern is from bundled library code, not malware. | ai | |
| source-diff | net-exec-file:dist/chunk-6SHF5RLP.js | AI (source-diff): Large esbuild bundle of oclif/core deps; net+exec pattern is from bundled node_modules, not malicious code. | ai | |
| phantom-deps | phantom-dep:@oclif/core | AI (phantom-deps): Same-org test plugin; @oclif/core is a declared runtime dep used indirectly via bundled dist. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-test-esm-1 | AI (phantom-deps): Same-org test plugin; referenced in oclif hooks config, not direct import. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-plugins | AI (phantom-deps): Same-org test plugin; dependency used indirectly in bundled output. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.5.142 | 3 / 16 | |
| 0.5.141 | 3 / 16 | |
| 0.5.140 | 3 / 16 | |
| 0.5.139 | 3 / 16 | |
| 0.5.138 | 3 / 16 | |
| 0.5.137 | 3 / 16 | |
| 0.5.136 | 3 / 16 | |
| 0.5.135 | 3 / 16 | |
| 0.5.134 | 3 / 16 | |
| 0.5.133 | 3 / 16 | |
| 0.5.132 | 3 / 16 | |
| 0.5.131 | 3 / 16 | |
| 0.5.130 | 3 / 16 | |
| 0.5.129 | 3 / 16 | |
| 0.5.128 | 3 / 16 | |
| 0.5.127 | 3 / 16 | |
| 0.5.126 | 3 / 16 | |
| 0.5.125 | 3 / 16 | |
| 0.5.124 | 3 / 16 | |
| 0.5.123 | 3 / 16 | |
| 0.5.122 | 3 / 16 | |
| 0.5.121 | 3 / 16 |
v0.5.142
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.141
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.140
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.138
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.136
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.135
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.134
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.133
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.132
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.131
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.130
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.129
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.128
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.127
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.