@picovoice/pvrecorder-node
Audio recorder sdk for Nodejs.
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Bundled .node files are platform-specific native audio recording bindings from Picovoice Inc., matching the package's documented purpose. Standard distribution pattern for native Node.js addons. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads the platform-appropriate bundled .node binary via getSystemLibraryPath(). This is the canonical pattern for native addon platform selection, not arbitrary code loading. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.2.9 | 0 / 13 | |
| 1.2.8 | 0 / 13 | |
| 1.2.7 | 0 / 13 | |
| 1.2.6 | 0 / 13 | |
| 1.2.5 | 0 / 13 | |
| 1.2.4 | 0 / 13 | |
| 1.2.3 | 0 / 13 | |
| 1.2.2 | 0 / 13 | |
| 1.2.1 | 0 / 13 | |
| 1.2.0 | 0 / 13 | |
| 1.1.2 | 0 / 5 | |
| 1.1.1 | 0 / 5 |
v1.2.7
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 (erismikpico) on 2025-03-21, 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.
v1.2.6
2 findingsThis version was published by a different npm account than previous versions on 2025-02-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.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 (erismikpico) than the most recent previously approved version (albho) on 2025-01-15, 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.
v1.2.4
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 (albho) than the most recent previously approved version (matt200-ok) on 2024-09-13, but albho 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.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
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 (erismikpico) than the most recent previously approved version (kyeo) on 2024-01-30, 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.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
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 (kyeo) than the most recent previously approved version (dynamix70) on 2023-07-12, 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.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.