@aa-sdk/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped Alchemy SDK package; name similarity to 'cors' is coincidental, not a squatting attempt. | ai |
Versions (showing 4 of 104)
| Version | Deps | Published |
|---|---|---|
| 4.32.0 | 3 / 5 | |
| 4.31.2 | 3 / 5 | |
| 4.31.1 | 3 / 5 | |
| 4.31.0 | 3 / 5 |
v4.32.0
2 findingsPackage name '@aa-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.31.2
2 findingsPackage name '@aa-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.31.1
2 findingsPackage name '@aa-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.31.0
2 findingsPackage name '@aa-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.