@picovoice/cheetah-node
Picovoice Cheetah Node.js binding
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Picovoice Cheetah ships prebuilt platform-specific native .node binaries as its documented distribution model; bundled binaries are expected and stable across all versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load the correct platform-specific native .node binary at runtime — standard pattern for multi-platform native Node.js addons. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 4.0.4 | 0 / 14 | |
| 4.0.1 | 0 / 14 | |
| 4.0.0 | 0 / 14 | |
| 3.0.0 | 0 / 14 |
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
2 findingsPackage contains compiled binaries that could be backdoors: • lib/windows/amd64/pv_ypu_impl_cuda_cheetah.dll • lib/linux/x86_64/pv_cheetah.node • lib/mac/arm64/pv_cheetah.node • lib/mac/x86_64/pv_cheetah.node • lib/raspberry-pi/cortex-a53-aarch64/pv_cheetah.node • lib/raspberry-pi/cortex-a53/pv_cheetah.node • lib/raspberry-pi/cortex-a72-aarch64/pv_cheetah.node • lib/raspberry-pi/cortex-a72/pv_cheetah.node • lib/raspberry-pi/cortex-a76-aarch64/pv_cheetah.node • lib/raspberry-pi/cortex-a76/pv_cheetah.node ... and 2 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.