@prosopo/procaptcha-bundle@4.6.5
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package contains disclosed, conditional runtime telemetry to Prosopo, but the beacon includes the page hostname and site key, which identify the site or project. That identifying telemetry warrants a warning; the inspected flow does not show credential theft or unrelated collection.
Decision evidence
public snapshot- Widget creation calls sendUsageBeacon with the configured site key.
- The beacon sends the page hostname, site key, bundle version, and sample rate to beacon.prosopo.io, with a 0.1% sampling rate.
- Sending is limited to builds with PROSOPO_PROVIDER_LIST and can be disabled with PROSOPO_USAGE_BEACON=false; the request omits credentials and the referrer.
- The changelog describes the beacon and its purpose as counting self-hosted installs.
- The package has no install lifecycle scripts in its metadata.
- The beacon is conditional, sampled, and sent to Prosopo’s own service; the changelog discloses it.
- The collected values identify the site or project, but the inspected code does not show credential or visitor-data collection.
Source & flagged code
6 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/esm/index.jsView on unpkg · L7Widget creation calls sendUsageBeacon with the configured site key.
dist/esm/util/widgetFactory.jsView on unpkg · L49Findings
Affected versions and remediation
This report applies to @prosopo/procaptcha-bundle@4.6.5.
See all versions of @prosopo/procaptcha-bundle for other recorded verdicts.
- Review the evidence and your use of @prosopo/procaptcha-bundle@4.6.5 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.