stablezact-pay@0.67.0
Beautiful and smooth blockchain payment gateway SDK for seamless crypto payments - React & vanilla js
AI Security Review
scanned 4mo ago · by lpm-firewall-aiScanner credential-exfiltration hints are explained by expected merchant API authentication headers in payment API clients and by wallet/payment SDK functionality. I found no install-time/import-time malicious execution, secret harvesting from env/files/storage, unauthorized endpoint, or AI-agent control-surface mutation beyond temporary browser meta tags for Coinley API/public-key discovery.
Decision evidence
public snapshot- package.json has no install/preinstall/postinstall/prepare lifecycle hooks.
- dist/index.esm.js only re-exports SDK symbols from bundled chunks; React payment UI is lazy-loaded.
- dist/CoinleyPayment-C6ChHSdL.js sends X-Public-Key or merchant-supplied X-API-Key/X-API-Secret only to caller-provided baseURL endpoints.
- Network calls are payment/bridge/wallet aligned: /api/payments/*, /api/networks/*, /api/bridge/*, li.quest, Alchemy/Jupiter token APIs.
- Browser storage use is limited to Coinley payment state/recovery keys, not credential harvesting.
- No filesystem access, child_process, shell execution, npm lifecycle execution, or persistence code found.
Source & flagged code
3 flaggedSource appears to send environment or credential material to an external endpoint.
dist/CoinleyPayment-C6ChHSdL.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to stablezact-pay@0.67.0.
See all versions of stablezact-pay for other recorded verdicts.
- Review the evidence and your use of stablezact-pay@0.67.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.