@picovoice/cheetah-web
Cheetah Speech-to-Text engine for web browsers (via WebAssembly)
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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 encodes rollup web-worker bundle; stable pattern across all versions of this package. | ai | |
| source-diff | encoded-string-file:dist/iife/index.js | AI (source-diff): Same rollup web-worker loader pattern; benign for this package. | ai | |
| source-diff | encoded-string-file:dist/esm/index.min.js | AI (source-diff): Minified build of same web-worker bundle; benign for this package. | ai | |
| source-diff | encoded-string-file:dist/iife/index.min.js | AI (source-diff): Minified IIFE build of same web-worker bundle; benign for this package. | ai | |
| provenance | no-provenance | AI (provenance): Picovoice packages predate widespread Sigstore adoption; absence of provenance is consistent across their entire catalog and not a risk indicator for this publisher. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.1.3 | 2 / 26 | |
| 4.1.2 | 2 / 26 | |
| 4.1.1 | 2 / 26 | |
| 4.1.0 | 1 / 26 | |
| 4.0.4 | 1 / 26 | |
| 4.0.3 | 1 / 26 | |
| 4.0.2 | 1 / 26 | |
| 4.0.1 | 1 / 26 | |
| 4.0.0 | 1 / 26 | |
| 3.0.0 | 1 / 26 |
v4.1.3
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 (erismikpico) than the most recent previously approved version (matt200-ok) on 2026-07-08, but erismikpico 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.
v4.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 (erismikpico) on 2026-06-30, 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.