@meteora-ag/zap-sdk
A Typescript SDK for interacting with the Zap program on Meteora.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Meteora packages consistently lack provenance; stable false positive for this org. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.3.2 | 8 / 13 | |
| 1.3.1 | 8 / 13 | |
| 1.3.0 | 8 / 13 | |
| 1.2.0 | 8 / 7 | |
| 1.1.2 | 8 / 7 | |
| 1.1.1 | 8 / 7 | |
| 1.0.6 | 8 / 4 | |
| 1.0.4 | 8 / 4 | |
| 1.0.3 | 7 / 4 | |
| 1.0.2 | 7 / 4 | |
| 1.0.1 | 7 / 4 | |
| 1.0.0 | 7 / 4 |
v1.3.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (senddageeand4get) than the most recent previously approved version (bangyro) on 2026-06-30, but senddageeand4get 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.