stablezact-pay@0.69.0
Beautiful and smooth blockchain payment gateway SDK for seamless crypto payments - React & vanilla js
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe scanner's credential-exfiltration hint is explained by a payment SDK sending caller-supplied merchant credentials to the caller-configured payment API, not harvesting ambient secrets. Static inspection found no lifecycle execution, persistence, destructive behavior, or unauthorized data collection beyond package-aligned runtime APIs and analytics.
Decision evidence
public snapshot- dist/CoinleyPayment-CgOyBTiZ.js sends user-provided apiKey/apiSecret or publicKey to configured baseURL during payment API calls
- dist/index-B1VDVZ7m.js includes Mixpanel/Clarity analytics code that can track SDK payment UI events
- package.json has no install/preinstall/postinstall lifecycle hooks or bin entries
- dist/index.esm.js only re-exports SDK components from built chunks
- dist/index-Ce7cAlPl.js requires caller-supplied apiUrl and credentials before opening payment UI
- dist/CoinleyPayment-CgOyBTiZ.js network calls are payment, bridge, wallet/RPC, and analytics functionality aligned with a crypto checkout SDK
- No child_process, fs writes, home/project agent config mutation, eval, or credential harvesting logic found in package-owned source
Source & flagged code
3 flaggedSource appears to send environment or credential material to an external endpoint.
dist/CoinleyPayment-CgOyBTiZ.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to stablezact-pay@0.69.0.
See all versions of stablezact-pay for other recorded verdicts.
- Review the evidence and your use of stablezact-pay@0.69.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.