@prosopo/procaptcha-bundle@4.6.0
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe inspected entry points and configuration support the package’s CAPTCHA rendering purpose, and the package declares no lifecycle scripts. The only identified telemetry is a 0.1% sampled beacon to Prosopo, gated on a provider-list setting and carrying the site host and key.
Decision evidence
public snapshot- The package exports browser-oriented ESM and CommonJS widget entry points and declares no lifecycle scripts.
- Startup renders CAPTCHA widgets from page elements when implicit rendering is configured; explicit rendering is also supported.
- Environment variables configure the site key and CAPTCHA environment/server settings.
- The usage beacon targets Prosopo, samples at 0.1%, and sends only when a provider-list override is present.
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 · L7Startup renders CAPTCHA widgets from page elements when implicit rendering is configured; explicit rendering is also supported.
dist/esm/index.jsView on unpkg · L224Findings
Affected versions and remediation
This report applies to @prosopo/procaptcha-bundle@4.6.0.
See all versions of @prosopo/procaptcha-bundle for other recorded verdicts.
- Review the evidence and your use of @prosopo/procaptcha-bundle@4.6.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.