@picovoice/picollm-node-demo
Picovoice PicoLLM Node.js chat and completion demos
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Picovoice org rotation; gabe-picovoice is a known org maintainer, not a suspicious takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Picovoice org rotation; removal of albho/liuatpico consistent with internal team changes. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by major version gap (1.3.1 → 2.1.2); consistent with upstream SDK release cycle. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Prettier is a formatting tool listed as a dependency but used only in config; a packaging hygiene issue, not a security risk. Stable for this demo package. | ai | |
| provenance | no-provenance | AI (provenance): Picovoice is a legitimate established company; lack of Sigstore provenance is common and not a risk indicator here. | ai |
v2.1.2
2 findings[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 (ilavery) 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.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.