@prosopo/procaptcha-bundle@4.4.1
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection found a browser CAPTCHA bundle with no lifecycle scripts or malicious primitives. Environment settings and dynamic imports are limited to configuring and loading its declared CAPTCHA dependencies.
Decision evidence
public snapshot- The manifest exposes a browser bundle and contains no install lifecycle hook.
- The built entry imports local modules and declared Prosopo CAPTCHA dependencies.
- Source config reads named CAPTCHA settings and passes them into a validated widget configuration.
- The widget mounts the declared CAPTCHA component; no direct credential harvesting, filesystem access, shell execution, or network primitive was found.
- Importing the browser entry performs widget initialization and may prefetch CAPTCHA detection after a caller supplies a site key.
- Environment-variable references configure the CAPTCHA service; they do not enumerate or exfiltrate the consumer environment.
- The scanner's runtime dependency bridge is consistent with declared dependencies and the bundle's widget role.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/index.jsView on unpkg · L5The built entry imports local modules and declared Prosopo CAPTCHA dependencies.
dist/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @prosopo/procaptcha-bundle@4.4.1.
See all versions of @prosopo/procaptcha-bundle for other recorded verdicts.
- Review the evidence and your use of @prosopo/procaptcha-bundle@4.4.1 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.