@prosopo/procaptcha-bundle@4.5.10
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the browser entrypoint’s inspected behavior is CAPTCHA widget initialization and control. Environment variables feed the widget configuration, but the package source inspected does not establish an attack or credential transfer.
Decision evidence
public snapshot- The manifest points to browser entrypoints and lists build and test scripts; it has no lifecycle hook.
- The entrypoint initializes CAPTCHA widgets and exposes ready, render, reset, remove, execute, and start.
- Detector prefetch requires a site key and is skipped in manual start mode.
- Environment values are placed in the CAPTCHA configuration and passed to the widget renderer; no credential transfer is established by the inspected package source.
Source & flagged code
6 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/index.jsView on unpkg · L5The entrypoint initializes CAPTCHA widgets and exposes ready, render, reset, remove, execute, and start.
dist/index.jsView on unpkg · L312Findings
Affected versions and remediation
This report applies to @prosopo/procaptcha-bundle@4.5.10.
See all versions of @prosopo/procaptcha-bundle for other recorded verdicts.
- Review the evidence and your use of @prosopo/procaptcha-bundle@4.5.10 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.