@picovoice/cheetah-react
React hook for Cheetah Web SDK
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 is an inlined Web Worker bundle from rollup-plugin-web-worker-loader; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/iife/index.js | AI (source-diff): Same inlined Web Worker bundle pattern; benign for this package. | ai | |
| source-diff | encoded-string-file:dist/esm/index.min.js | AI (source-diff): Minified build with inlined Web Worker; same benign pattern. | ai | |
| source-diff | encoded-string-file:dist/iife/index.min.js | AI (source-diff): Minified IIFE build with inlined Web Worker; same benign pattern. | ai | |
| provenance | no-provenance | AI (provenance): Picovoice SDK packages consistently lack Sigstore provenance; this is a stable characteristic of the publisher, not a risk indicator. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.0.4 | 1 / 30 | |
| 4.0.3 | 1 / 30 | |
| 4.0.2 | 1 / 30 | |
| 4.0.1 | 1 / 30 | |
| 4.0.0 | 1 / 30 | |
| 3.0.0 | 1 / 30 |
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
6 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 5 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 (ilavery) than the most recent previously approved version (erismikpico) on 2026-05-12, but ilavery 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.0.2
6 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 5 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 (kyeo) than the most recent previously approved version (erismikpico) on 2026-05-06, but kyeo 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.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.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.
v3.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.