@prosopo/procaptcha-bundle@4.2.3
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe flagged environment-variable and dynamic-import behavior configures and prefetches named captcha dependencies during widget rendering. The package has no registry install hook or concrete malicious behavior in the inspected source.
Decision evidence
public snapshot- The runtime entry point dynamically loads Prosopo captcha modules and calls their detector-prefetch API with a supplied site key.
- Configuration reads Prosopo environment settings, including optional server and event-store URLs.
- The manifest exposes browser bundle entry points and contains build/test scripts, not an install lifecycle hook.
- No install, preinstall, or postinstall hook is declared.
- No source-owned network endpoint, credential harvesting, filesystem access, shell execution, or dynamic code evaluation was found.
- The inspected code mounts and manages a browser captcha widget; the dynamic imports are named package dependencies.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/index.jsView on unpkg · L4The runtime entry point dynamically loads Prosopo captcha modules and calls their detector-prefetch API with a supplied site key.
dist/index.jsView on unpkg · L35Findings
Affected versions and remediation
This report applies to @prosopo/procaptcha-bundle@4.2.3.
See all versions of @prosopo/procaptcha-bundle for other recorded verdicts.
- Review the evidence and your use of @prosopo/procaptcha-bundle@4.2.3 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.