@mayanfinance/swap-sdk
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.iife.min.js | AI (source-diff): Long encoded strings are expected in the minified IIFE bundle; sample shows native-addon loader logic, not malicious payload. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 14.3.0 | 8 / 3 | |
| 14.2.0 | 8 / 3 | |
| 14.1.0 | 8 / 3 | |
| 14.0.0 | 8 / 3 | |
| 13.3.0 | 8 / 3 | |
| 13.2.0 | 8 / 3 | |
| 13.1.0 | 8 / 3 | |
| 13.0.0 | 8 / 3 | |
| 12.2.5 | 8 / 3 | |
| 12.2.4 | 8 / 3 | |
| 12.2.3 | 8 / 3 | |
| 12.2.2 | 8 / 3 | |
| 12.2.1 | 8 / 3 | |
| 12.2.0 | 8 / 3 | |
| 12.1.0 | 8 / 3 | |
| 12.0.0 | 8 / 3 |
v14.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
2 findingsModified file contains 8 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.
v14.0.0
2 findingsModified file contains 8 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.
v13.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.0
2 findingsModified file contains 8 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.
v13.1.0
2 findingsModified file contains 8 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.
v13.0.0
2 findingsModified file contains 8 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.
v12.2.5
2 findingsModified file contains 8 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.
v12.2.4
2 findingsModified file contains 8 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.
v12.2.3
2 findingsModified file contains 8 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.
v12.2.2
2 findingsModified file contains 8 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.
v12.2.1
2 findingsModified file contains 8 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.
v12.2.0
2 findingsModified file contains 8 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.
v12.1.0
2 findingsModified file contains 8 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.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.