@picovoice/leopard-node-demo
Picovoice Leopard Node.js file-based and microphone 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, 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@picovoice/leopard-node | AI (dependencies): First-party Picovoice dependency; expected and legitimate for this demo package. | ai | |
| dependencies | unvetted-dep:@picovoice/pvrecorder-node | AI (dependencies): First-party Picovoice dependency for microphone recording; expected and legitimate for this demo package. | ai | |
| dependencies | unvetted-dep:wavefile | AI (dependencies): Well-known audio file library; appropriate dependency for a speech recognition demo. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Prettier listed as dependency for formatting; not a security concern for this demo package. | ai | |
| phantom-deps | phantom-dep:wavefile | AI (phantom-deps): wavefile may be used indirectly; not a security concern for this established demo package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.0.6 | 6 / 0 | |
| 2.0.5 | 6 / 0 | |
| 2.0.4 | 6 / 0 | |
| 2.0.3 | 6 / 0 | |
| 2.0.2 | 6 / 0 | |
| 2.0.1 | 6 / 0 |
v2.0.5
2 findingsPackage 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 (albho) on 2025-01-16, 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.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.