@alipay/ams-checkout@2.0.30
Use _AMS CHECKOUT_ as an ES module.
AI Security Review
scanned 16d ago · by lpm-firewall-aiInspected source supports ordinary checkout SDK requests and Alipay logging, while the flagged IP is part of serialized example configuration. No concrete malicious behavior was established, so mark clean.
Decision evidence
public snapshot- package.json exposes checkout entrypoints and its only lifecycle hook runs Husky setup.
- The flagged IP is embedded as a checkout example image URL; runtime logging uses Alipay collection endpoints, and API-bus requests forward supplied request data through the request service.
- The inspected runtime and type-definition paths contain SDK exports, request utilities, API-bus interfaces, and declarations; no credential harvesting or unrelated credential recipient was identified.
- The scanner flagged a hardcoded runtime exfiltration pattern, dynamic require, and network behavior; inspection found the IP in serialized example configuration and the network code in SDK logging/request flows.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
ams-checkout.jsView on unpkg · L5A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
ams-checkout.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to @alipay/ams-checkout@2.0.30.
See all versions of @alipay/ams-checkout for other recorded verdicts.
- Review the evidence and your use of @alipay/ams-checkout@2.0.30 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.