@picovoice/porcupine_manager
wake word detection & voice command engine running locally in browser
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall only copies files from a same-org sibling package, no network/exec. | ai | |
| source-diff | obfuscated-file:src/pv_porcupine.js | AI (source-diff): Emscripten-generated WASM loader glue, not malicious obfuscation. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): WASM is the core on-device speech engine, documented and expected. | ai | |
| phantom-deps | phantom-dep:@picovoice/web-voice-processor | AI (phantom-deps): Same-org dependency from @picovoice scope; declared as a runtime dep and consistent with Picovoice's modular SDK architecture across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Picovoice package predating Sigstore provenance adoption; absence is expected for packages of this age. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 1 / 0 | |
| 1.2.0 | 1 / 0 | |
| 1.1.0 | 1 / 0 | |
| 1.0.11 | 1 / 0 | |
| 1.0.10 | 1 / 0 | |
| 1.0.9 | 1 / 0 | |
| 1.0.6 | 1 / 0 | |
| 1.0.5 | 1 / 0 | |
| 1.0.4 | 1 / 0 | |
| 1.0.2 | 1 / 0 | |
| 1.0.1 | 1 / 0 |
v1.2.0
3 findingsPackage contains compiled binaries that could be backdoors: • src/pv_porcupine.wasm
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
3 findingsPackage contains compiled binaries that could be backdoors: • src/pv_porcupine.wasm
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
3 findingsPackage contains compiled binaries that could be backdoors: • src/pv_porcupine.wasm
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
3 findingsPackage contains compiled binaries that could be backdoors: • src/pv_porcupine.wasm
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
3 findingsPackage contains compiled binaries that could be backdoors: • src/pv_porcupine.wasm
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
3 findingsPackage contains compiled binaries that could be backdoors: • src/pv_porcupine.wasm
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
3 findingsPackage contains compiled binaries that could be backdoors: • src/pv_porcupine.wasm
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
4 findingsScript: script/postinstall.sh
Package contains compiled binaries that could be backdoors: • src/pv_porcupine.wasm • src/pv_porcupine.wasm_symlink
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
4 findingsScript: script/postinstall.sh
Package contains compiled binaries that could be backdoors: • src/pv_porcupine.wasm
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.