@picovoice/picollm-web
picoLLM Inference Engine is a highly accurate and cross-platform SDK optimized for running compressed large language models.
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 | encoded-string-file:dist/esm/index.js | AI (source-diff): Base64 strings are inlined Web Worker bundles from rollup-plugin-web-worker-loader; stable build pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/iife/index.js | AI (source-diff): Same inlined Web Worker bundle pattern; not a malicious payload. | ai | |
| source-diff | encoded-string-file:dist/esm/index.min.js | AI (source-diff): Minified build with same inlined worker; expected artifact of this package's build process. | ai | |
| source-diff | encoded-string-file:dist/iife/index.min.js | AI (source-diff): Minified IIFE build with same inlined worker; expected artifact of this package's build process. | ai | |
| provenance | no-provenance | AI (provenance): Picovoice is an established company; lack of Sigstore provenance is common and not a risk signal for this package. | ai |
v2.1.2
6 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (matt200-ok) than the most recent previously approved version (erismikpico) on 2026-06-09, but matt200-ok is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.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.