@acala-network/sdk-swap
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Legitimate SDK sub-module; sparse README and no keywords are typical for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@acala-network/types | AI (phantom-deps): Same-org peer dependency declared but not directly imported; stable false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 4.1.15 | 5 / 1 | |
| 4.1.14 | 5 / 1 | |
| 4.1.11 | 5 / 1 | |
| 4.1.10 | 5 / 1 |
v4.1.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aniiantt) than the most recent previously approved version (xlc) on 2025-05-03, but aniiantt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.