@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 1.47.2 | 2 / 25 | |
| 1.47.1 | 2 / 25 | |
| 1.47.0 | 2 / 25 | |
| 1.46.0 | 2 / 25 |
v2.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
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.14
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
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.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.