@prosopo/procaptcha-bundle@4.2.2
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection found a package-aligned browser captcha implementation with no lifecycle hook or concrete malicious behavior. The randomized build chunk naming is a non-runtime build detail and does not establish an attack chain.
Decision evidence
public snapshot- The bundle dynamically imports related captcha modules and starts detector prefetch only when a site key is supplied.
- The development build configuration randomizes browser chunk names, but it is not an install hook or runtime payload in the published entrypoint.
- package.json declares no preinstall, install, or postinstall hook.
- The runtime code is a browser captcha widget that mounts React UI, handles widget events, and exposes a window API.
- No credential harvesting, filesystem access, shell execution, eval, remote URL, or network client appears in the shipped runtime source.
- The environment variables configure captcha settings; their values are passed into a configuration object rather than collected or exfiltrated.
Source & flagged code
3 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/index.jsView on unpkg · L4The bundle dynamically imports related captcha modules and starts detector prefetch only when a site key is supplied.
src/index.tsView on unpkg · L81Findings
Affected versions and remediation
This report applies to @prosopo/procaptcha-bundle@4.2.2.
See all versions of @prosopo/procaptcha-bundle for other recorded verdicts.
- Review the evidence and your use of @prosopo/procaptcha-bundle@4.2.2 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.