registry / @prosopo/procaptcha-bundle / 4.4.4
@prosopo/procaptcha-bundle@4.4.4
AI Security Review
scanned 2mo ago · by lpm-firewall-aiStatic inspection found a CAPTCHA browser bundle with package-aligned dynamic imports but no lifecycle hook or concrete malicious behavior. The environment-variable references configure the widget rather than harvesting the host environment.
Static reason
One or more suspicious static signals were detected.
Trigger
A site imports the bundle or renders a Procaptcha widget.
Impact
No installation-time mutation, local data collection, or package-owned exfiltration was found.
Mechanism
Loads CAPTCHA components and mounts them in the page DOM.
AI rationale
Static inspection found a CAPTCHA browser bundle with package-aligned dynamic imports but no lifecycle hook or concrete malicious behavior. The environment-variable references configure the widget rather than harvesting the host environment.
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The browser entrypoint dynamically loads Prosopo captcha dependencies and calls their detector prefetch with a site key.
- The manifest exposes browser module entrypoints and lists build/test scripts; it has no install lifecycle hook.
- The manifest declares a module entrypoint at dist/index.js and marks the package side-effect-free.
Evidence against
- No package code invokes shell commands, reads local files at runtime, harvests credentials, or exfiltrates data.
- The shipped entrypoint mounts and manages CAPTCHA widgets in the page DOM; no confirmed attack surface is established.
Behavioral surface
CryptoEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
3 flaggeddist/index.jsView file
5package = @prosopo/procaptcha-bundle; repositoryIdentity = captcha; dependency = @prosopo/procaptcha-common
L5: import { WidgetThemeResolver } from "./util/widgetThemeResolver.js";
L6: import { getWindowCallback } from "@prosopo/procaptcha-common";
L7: import { PROCAPTCHA_START_EVENT, StartModeEnum } from "@prosopo/types";
High
Copied Package Dependency Bridge
Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/index.jsView on unpkg · L538var startDetectorPrefetch = (siteKey, flags) => {
if (!siteKey) return;
if (flags.startMode === StartModeEnum.manual) return;
Promise.all([import("@prosopo/procaptcha-frictionless"), import("@prosopo/procaptcha-common")]).then(([frictionless, common]) => {
frictionless.prefetchDetector(process.env.PROSOPO_DEFAULT_ENVIRONMENT, common.pickIpMode(flags), siteKey);
}).catch(() => void 0);
Low
Suspicious Dependency Evidence
The browser entrypoint dynamically loads Prosopo captcha dependencies and calls their detector prefetch with a site key.
dist/index.jsView on unpkg · L38package.jsonView file
Findings
1 High2 Medium6 Low
HighCopied Package Dependency Bridgedist/index.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Dependency Evidencedist/index.js
LowAi Review Evidencepackage.json
Affected versions and remediation
This report applies to @prosopo/procaptcha-bundle@4.4.4.
See all versions of @prosopo/procaptcha-bundle for other recorded verdicts.
- Review the evidence and your use of @prosopo/procaptcha-bundle@4.4.4 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.