registry / @prosopo/procaptcha-bundle / 4.4.2
@prosopo/procaptcha-bundle@4.4.2
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe flagged environment access configures the captcha widget, while the bundled dependency imports are ordinary declared dependencies. Source inspection found no lifecycle hook or concrete malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
A host page renders a Procaptcha widget with a site key.
Impact
No unconsented install-time mutation, file access, command execution, or package-level data exfiltration was found.
Mechanism
Browser captcha rendering and provider prefetch.
AI rationale
The flagged environment access configures the captcha widget, while the bundled dependency imports are ordinary declared dependencies. Source inspection found no lifecycle hook or concrete malicious behavior.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest lists build and test commands but no install lifecycle hook.
- The published entry imports declared Prosopo and UI dependencies normally.
- Runtime prefetches the declared captcha provider only after a site key is supplied.
- Environment values are used as captcha configuration fields, not read from files or sent by this package.
Evidence against
- No package code invokes shells, writes files, harvests credentials, or exfiltrates data.
- The static dependency-bridge finding is explained by normal imports in the bundled entry point.
Behavioral surface
CryptoEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
5 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 · L51import "./_virtual/_rolldown/runtime.js";
import { extractParams, getProcaptchaScript } from "./util/config.js";
import { resolveStartMode } from "./util/startMode.js";
import { WidgetFactory } from "./util/widgetFactory.js";
import { WidgetThemeResolver } from "./util/widgetThemeResolver.js";
import { getWindowCallback } from "@prosopo/procaptcha-common";
import { PROCAPTCHA_START_EVENT, StartModeEnum } from "@prosopo/types";
import { at } from "@prosopo/util";
Low
Suspicious Dependency Evidence
The published entry imports declared Prosopo and UI dependencies normally.
dist/index.jsView on unpkg · L1package.jsonView file
Findings
1 High2 Medium8 Low
HighCopied Package Dependency Bridgedist/index.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Dependency Evidencedist/index.js
LowAi Review Evidencesrc/index.ts
LowAi Review Evidencesrc/util/configCreator.ts
Affected versions and remediation
This report applies to @prosopo/procaptcha-bundle@4.4.2.
See all versions of @prosopo/procaptcha-bundle for other recorded verdicts.
- Review the evidence and your use of @prosopo/procaptcha-bundle@4.4.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.