@prosopo/procaptcha-bundle@4.5.15
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe inspected manifest and runtime entrypoint show widget setup and guarded provider prefetch, with no concrete attack behavior identified. The environment setting is passed to the provider prefetch path, while the manifest has no install lifecycle hook.
Decision evidence
public snapshot- The manifest points the package entrypoints to the inspected ESM and CommonJS bundles and lists build scripts; no install lifecycle hook was found.
- The detector prefetch requires a site key and skips manual start mode before loading provider modules.
- Bundle startup sets up implicit rendering according to script parameters and document readiness; the exported API provides widget operations.
Source & flagged code
6 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/index.jsView on unpkg · L6The detector prefetch requires a site key and skips manual start mode before loading provider modules.
dist/index.jsView on unpkg · L41Findings
Affected versions and remediation
This report applies to @prosopo/procaptcha-bundle@4.5.15.
See all versions of @prosopo/procaptcha-bundle for other recorded verdicts.
- Review the evidence and your use of @prosopo/procaptcha-bundle@4.5.15 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.