registry / @connect-xyz/auth-react / 0.84.7
@connect-xyz/auth-react@0.84.7
A React SDK that enables frontend React applications to seamlessly integrate with the Connect Auth product.
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no install hook, and the runtime behavior inspected is consistent with loading the authentication SDK and reporting script-load failures to the configured product collector. The network activity and diagnostic fields do not establish a malicious attack.
Static reason
No blocking static signals were detected.
Trigger
Rendering the component in a browser starts SDK loading; a load failure triggers diagnostic reporting.
Impact
The package sends failure diagnostics to its default Zerohash collector; the inspected source does not establish credential theft or other malicious behavior.
Mechanism
The failure report contains app and script details, selected JWT claims, browser user agent, and page origin, then is sent by an HTTP POST.
AI rationale
The manifest has no install hook, and the runtime behavior inspected is consistent with loading the authentication SDK and reporting script-load failures to the configured product collector. The network activity and diagnostic fields do not establish a malicious attack.
Evidence
package.jsondist/index.js
Network endpoints3
sdk.sandbox.connect.xyz/auth-web/index.jssdk.connect.xyz/auth-web/index.jsgrafana-faro-collector.zerohash.com/collect
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json points to the runtime bundle and declares no install lifecycle scripts.
- The React component loads the authentication web SDK from the package’s Connect XYZ sandbox or production host.
- On a script-load failure, the bundle builds diagnostic data from app and script details, selected JWT claims, browser user agent, and page origin.
- The bundle posts those diagnostics to its configured collector; the default collectors are Zerohash endpoints.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
6 flaggedpackage.jsonView file
1{
"name": "@connect-xyz/auth-react",
"version": "0.84.7",
"private": false,
"type": "module",
"main": "./dist/index.js",
"module": "./dist/index.js",
"types": "./dist/index.d.ts",
"license": "MIT",
"exports": {
"./package.json": "./package.json",
".": {
"types": "./dist/index.d.ts",
"import": "./dist/index.js",
"default": "./dist/index.js"
}
},
"files": [
"dist",
"!**/*.tsbuildinfo"
],
"nx": {
"name": "auth-react"
},
"peerDependencies": {
"react": ">=18.0.0",
"react-dom": ">=18.0.0"
}
}
Low
Suspicious Lifecycle Evidence
package.json points to the runtime bundle and declares no install lifecycle scripts.
package.jsonView on unpkg · L1dist/index.jsView file
276env: d,
jwt: f,
timeoutMs: p,
onError: () => h(!0)
})), [
t,
n,
a,
s,
c,
l,
d,
f,
p,
g
]), {
loadFailed: m,
retry: r(() => _((e) => e + 1), [])
};
}, C = {
sandbox: "https://sdk.sandbox.connect.xyz/auth-web/index.js",
production: "https://sdk.connect.xyz/auth-web/index.js"
}, w = "connect-auth", T = C, E = ({ jwt: t, env: r = "production", theme: i, onError: o, onClose: s, onDeposit
Low
Ai Review Evidence
The React component loads the authentication web SDK from the package’s Connect XYZ sandbox or production host.
Findings
1 Medium7 Low
MediumNetwork
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
Affected versions and remediation
This report applies to @connect-xyz/auth-react@0.84.7.
See all versions of @connect-xyz/auth-react for other recorded verdicts.
- Review the evidence and your use of @connect-xyz/auth-react@0.84.7 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.