@prosopo/procaptcha-bundle@4.5.21
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package’s metadata and runtime entry points match a browser CAPTCHA bundle: import-time behavior initializes widget integration, and prefetch is tied to a supplied site key. The scanner’s runtime-bridge and environment-variable flags correspond to a `node:module` import and Prosopo configuration reads; I found no unrelated credential flow or install-time behavior.
Decision evidence
public snapshot- Package exports CAPTCHA widget entry points; its declared scripts are for building, serving and testing, with no install lifecycle hooks or bin entry.
- Import setup publishes the widget API and ready event, then boots the CAPTCHA page integration.
- Detector prefetch requires a site key and is skipped in manual start mode; it passes the widget’s site key, language and integration to Prosopo dependencies.
- Environment reads configure Prosopo environment, site key, server URL and events URI; I found no code that searches for user credentials or sends them elsewhere.
- The flagged virtual runtime bridge contains only an import of node:module.
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 · L7Import setup publishes the widget API and ready event, then boots the CAPTCHA page integration.
dist/esm/index.jsView on unpkg · L304Findings
Affected versions and remediation
This report applies to @prosopo/procaptcha-bundle@4.5.21.
See all versions of @prosopo/procaptcha-bundle for other recorded verdicts.
- Review the evidence and your use of @prosopo/procaptcha-bundle@4.5.21 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.