@across-protocol/app-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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:aws-sdk | AI (typosquat): Scoped package @across-protocol/app-sdk is a legitimate bridge SDK, not a typosquat of aws-sdk. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 1 / 14 | |
| 0.4.4 | 0 / 15 | |
| 0.4.3 | 0 / 15 | |
| 0.4.2 | 0 / 15 | |
| 0.4.0 | 0 / 15 | |
| 0.3.0 | 0 / 15 | |
| 0.2.3 | 0 / 15 | |
| 0.2.2 | 0 / 15 |
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.