@1interface/voice-core@0.2.0
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe lifecycle hook is unusual but only targets relative dependency paths and is not coupled to exfiltration, payload loading, or AI-agent control-surface mutation. Runtime network and microphone operations are package-aligned voice functionality activated by consumer interaction.
Decision evidence
public snapshot- package.json defines a postinstall command that removes relative node_modules/react and node_modules/react-dom paths.
- dist/index.mjs only fetches API_ENDPOINTS.WEBRTC_ICE during voice connection setup.
- dist/index.mjs requests microphone access only through enterVoiceMode and navigator.mediaDevices.
- dist/index.mjs stores only selected audio-device IDs through the supplied storage abstraction.
- Inspected package code has no child-process, filesystem, environment-harvesting, eval, or literal exfiltration endpoint behavior.
- dist/index.d.ts describes a React/browser voice client API, matching the observed runtime code.
Source & flagged code
2 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @1interface/voice-core@0.2.0.
See all versions of @1interface/voice-core for other recorded verdicts.
- Review the evidence and your use of @1interface/voice-core@0.2.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.