@vocoder/plugin
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-D3OZSJ27.mjs | AI (source-diff): Large chunk is a tsup/esbuild bundle of node_modules; boilerplate pattern visible in sample, not dropper code. | ai | |
| source-diff | net-exec-file:dist/chunk-NDT5SGUG.mjs | AI (source-diff): Large bundled chunk is tsup output bundling @babel/parser and similar deps; standard build-tool pattern for this package. | ai | |
| source-diff | net-exec-file:dist/chunk-ZTGRNMIH.mjs | AI (source-diff): Large chunk is a tsup-bundled build artifact containing @babel/parser and esbuild interop shims; not malicious network+exec behavior. | ai | |
| source-diff | net-exec-file:dist/chunk-4FSC6KMN.mjs | AI (source-diff): Large bundled build artifact with babel/parser and CJS interop boilerplate; network+dynamic-require pattern is expected for this i18n build plugin. | ai | |
| source-diff | net-exec-file:dist/chunk-WZZM2ZNK.mjs | AI (source-diff): Large chunk is tsup-bundled output inlining @babel/parser; dynamic require shims are standard bundler boilerplate, not malicious. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 1 / 6 | |
| 0.16.4 | 1 / 6 | |
| 0.16.3 | 1 / 6 | |
| 0.16.2 | 1 / 6 | |
| 0.16.1 | 1 / 6 | |
| 0.16.0 | 1 / 6 | |
| 0.14.0 | 1 / 5 | |
| 0.13.4 | 1 / 5 | |
| 0.13.3 | 1 / 5 | |
| 0.13.2 | 1 / 5 | |
| 0.13.1 | 1 / 5 | |
| 0.13.0 | 1 / 5 | |
| 0.12.3 | 1 / 5 | |
| 0.12.2 | 1 / 5 | |
| 0.12.1 | 1 / 5 | |
| 0.8.1 | 1 / 5 | |
| 0.2.4 | 2 / 4 | |
| 0.2.3 | 2 / 4 |
v0.18.0
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.16.4
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.16.3
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.16.2
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.16.1
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.16.0
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.14.0
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.13.4
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.13.3
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.13.2
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.13.1
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.13.0
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.12.3
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.12.2
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.12.1
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.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.