@lydianpay/sdk-web@3.15.0
Drop-in crypto payment checkout for the web — a <lydian-checkout> web component and window.Lydian API across 20+ chains and major stablecoins.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged credential flow uses session-provided values for the corresponding event API, and the inspected telemetry submission path is gated by `telemetryEnabled`. The observed network behavior is consistent with the package’s web checkout and WalletConnect SDK purpose.
Decision evidence
public snapshot- The package entry resolves to its SDK bundle, consistent with its stated web checkout purpose.
- WalletConnect event telemetry is controlled by the `telemetryEnabled` option; without it, the event client does not submit queued events.
- The flagged `Authorization` header is built from a session ID and supplied session value, then used for that session’s event API.
- The device-token request sends a caller-supplied token to the project’s clients endpoint, consistent with notification registration.
- The SDK bundle uses network APIs and includes WalletConnect telemetry code, but the inspected event-submission path is gated by the telemetry option.
- The flagged credential flow uses session-specific values rather than reading environment variables or unrelated local credentials.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/chunks/index-FAg0du7P.jsView on unpkg · L26Source appears to send environment or credential material to an external endpoint.
dist/chunks/mountEngine-0Lj7ZkFh.jsFindings
Affected versions and remediation
This report applies to @lydianpay/sdk-web@3.15.0.
See all versions of @lydianpay/sdk-web for other recorded verdicts.
- Review the evidence and your use of @lydianpay/sdk-web@3.15.0 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.