@prosopo/procaptcha-bundle@4.6.1
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe entry point and detector prefetch serve the CAPTCHA widget's purpose, and the flagged module bridge is only a generated runtime import. The only identified reporting is sampled runtime telemetry disclosed in the changelog, sent to Prosopo with a build-time opt-out.
Decision evidence
public snapshot- The package exports a browser CAPTCHA widget entry point and declares no install lifecycle scripts.
- Detector prefetch uses the site key and CAPTCHA options, and skips manual-start widgets.
- The changelog discloses the self-hosted usage beacon, its data, and how to disable it.
- The beacon is limited to builds with a provider-list override and samples about one render in a thousand; it sends the page hostname, site key, bundle version, and sample rate without cookies or a referrer.
- The flagged Rolldown runtime bridge only imports node:module and exports an empty 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 · L7Detector prefetch uses the site key and CAPTCHA options, and skips manual-start widgets.
dist/esm/index.jsView on unpkg · L44Findings
Affected versions and remediation
This report applies to @prosopo/procaptcha-bundle@4.6.1.
See all versions of @prosopo/procaptcha-bundle for other recorded verdicts.
- Review the evidence and your use of @prosopo/procaptcha-bundle@4.6.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.