kasookoo-click-to-call-widget@0.1.0-beta.24
Framework-agnostic click-to-call widget for Kasookoo — a built-in dialer and call window that places outbound SIP/phone calls over WebRTC.
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe manifest has no install-time hook; its prepublish-only script runs a build. Runtime credentials are used with the configured Kasookoo API, and the fixed telemetry destination receives correlation identifiers rather than session credentials, so the inspected behavior does not establish a malicious attack surface.
Decision evidence
public snapshot- The manifest exposes browser and CommonJS runtime entrypoints; its only lifecycle script is a prepublish-only build.
- Session creation sends the publishable key and subject to the configured Kasookoo API. Bearer tokens are attached conditionally to API requests; calls pass through the widget’s call flow.
- Widget initialization starts telemetry to a fixed Kasookoo monitoring endpoint, where spans include request, call-trace, and user identifiers. The inspected flow does not send session tokens or passwords to that endpoint.
- The browser bundle contains corresponding session, call, and telemetry flows. Targeted searches found no eval, Function constructor, or child-process usage.
- Telemetry starts during widget initialization and sends correlation and user identifiers to the fixed monitoring endpoint.
Source & flagged code
4 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/kasookoo-dialer.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to kasookoo-click-to-call-widget@0.1.0-beta.24.
See all versions of kasookoo-click-to-call-widget for other recorded verdicts.
- Review the evidence and your use of kasookoo-click-to-call-widget@0.1.0-beta.24 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.