@ensnode/ponder-sdk
A utility library for interacting with Ponder apps and data.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:parse-prometheus-text-format | AI (dependencies): parse-prometheus-text-format is a legitimate, stable npm package for Prometheus metric parsing with no known advisories. Its use here is appropriate for a Ponder SDK utility. | ai | |
| phantom-deps | phantom-dep:parse-prometheus-text-format | AI (phantom-deps): parse-prometheus-text-format is a declared runtime dependency; phantom-dep firing because it's used indirectly or in config rather than direct import is a stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.15.1 | 1 / 7 | |
| 1.15.0 | 1 / 7 | |
| 1.14.0 | 1 / 7 | |
| 1.13.1 | 1 / 7 | |
| 1.13.0 | 1 / 7 | |
| 1.12.0 | 1 / 7 | |
| 1.11.1 | 1 / 7 | |
| 1.11.0 | 1 / 7 | |
| 1.10.1 | 1 / 7 | |
| 1.10.0 | 1 / 7 | |
| 1.9.0 | 1 / 7 | |
| 1.6.0 | 1 / 7 |
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.