@alipay/ams-checkout
Use _AMS CHECKOUT_ as an ES module.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:esm/modern/index.js | AI (source-diff): Babel-transpiled helper code (regeneratorRuntime), not obfuscation. | ai | |
| source-diff | net-exec-file:dist/ams-checkout.min.js | AI (source-diff): Minified bundle output of same SDK. | ai | |
| source-diff | obfuscated-file:esm/util/beforeConfirm.js | AI (source-diff): Babel-transpiled helper code, not true obfuscation. | ai | |
| source-diff | obfuscated-file:ams-checkout.js | AI (source-diff): Standard UMD bundle output, not true obfuscation. | ai | |
| source-diff | net-exec-file:ams-checkout.js | AI (source-diff): Bundled polyfill/base64 code, no malicious network+exec behavior found. | ai | |
| source-diff | obfuscated-file:esm/main.js | AI (source-diff): Babel-generated helper output, not obfuscation. | ai | |
| source-diff | encoded-string-file:dist/umd/ams-checkout.min.js | AI (source-diff): Minified bundle strings, not hidden payloads. | ai | |
| source-diff | encoded-string-file:ams-checkout.js | AI (source-diff): Long strings are i18n locale data (Arabic/German/Greek/etc.) in a minified bundle, not obfuscated payloads. | ai | |
| source-diff | encoded-string-file:dist/ams-checkout.min.js | AI (source-diff): Same i18n locale data in the minified dist file; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP appears inside a mock/test data string literal, not a live network request. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2.0.20 | 4 / 32 | |
| 2.0.19 | 4 / 32 | |
| 2.0.18 | 4 / 32 | |
| 2.0.17 | 4 / 32 | |
| 2.0.16 | 4 / 32 | |
| 2.0.14 | 4 / 32 | |
| 2.0.13 | 4 / 32 | |
| 2.0.12 | 4 / 32 | |
| 2.0.11 | 4 / 32 | |
| 2.0.10 | 4 / 32 | |
| 2.0.9 | 4 / 32 | |
| 2.0.8 | 3 / 27 | |
| 2.0.7 | 3 / 27 | |
| 2.0.6 | 3 / 27 | |
| 2.0.5 | 3 / 27 | |
| 2.0.3 | 3 / 27 | |
| 2.0.2 | 3 / 27 | |
| 2.0.1 | 3 / 27 | |
| 2.0.0 | 3 / 27 | |
| 1.47.2 | 2 / 25 | |
| 1.47.1 | 2 / 25 | |
| 1.47.0 | 2 / 25 | |
| 1.46.0 | 2 / 25 |
v2.0.20
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.