@alipay/ams-checkout@2.0.29
Use _AMS CHECKOUT_ as an ES module.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection found ordinary package entrypoints and a prepare-only Husky command. The runtime tracker loader alone is package-aligned browser telemetry, not concrete malicious behavior.
Decision evidence
public snapshot- Package metadata maps the public ESM and CommonJS entrypoints to local checkout bundles.
- The only lifecycle-like script inspected is a prepare-time Husky setup command.
- The required bundle contains a fixed browser tracker-script loader for a named Marmot Cloud asset.
- The bundle dynamically loads a remote tracker asset at browser runtime, but the inspected code ties it to checkout telemetry and shows no concrete credential harvesting, local execution, or unconsented install-time mutation.
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.29.
See all versions of @alipay/ams-checkout for other recorded verdicts.
- Review the evidence and your use of @alipay/ams-checkout@2.0.29 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.