@uma-sdk/core
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
coreymartinjeremyatlightspark
Keywords
bitcoinlightningpaymentstypescript
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped UMA payments SDK; name similarity to 'cors' is coincidental, not impersonation. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding used for cryptographic public key handling in a payments SDK; expected and benign. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 3 / 16 |
v1.5.0
2 findings
HIGH
typosquat.levenshtein: Possible typosquat of 'cors'
typosquat
Package name '@uma-sdk/core' is 1 edit(s) away from popular package 'cors'.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.