← Home

@ensnode/ponder-subgraph

npm Repository Homepage

A Hono middleware for generating Subgraph-compatible GraphQL schema.

24
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

lightwalker_ethnotrabshrugs-namehash

Keywords

PonderSubgraph

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@ponder/client AI (dependencies): @ponder/client is a legitimate dependency from the Ponder indexing framework, appropriate for this package's purpose. ai
dependencies unvetted-dep:@escape.tech/graphql-armor-max-depth AI (dependencies): @escape.tech/graphql-armor-max-depth is a legitimate GraphQL security package from Escape.tech; appropriate for a GraphQL middleware package. ai
dependencies unvetted-dep:@escape.tech/graphql-armor-max-tokens AI (dependencies): @escape.tech/graphql-armor-max-tokens is a legitimate GraphQL security package from Escape.tech; appropriate for a GraphQL middleware package. ai
dependencies unvetted-dep:@escape.tech/graphql-armor-max-aliases AI (dependencies): @escape.tech/graphql-armor-max-aliases is a legitimate GraphQL security package from Escape.tech; appropriate for a GraphQL middleware package. ai

Versions (showing 24 of 24)

Version Deps Published
1.15.1 9 / 5
1.15.0 9 / 5
1.14.0 9 / 5
1.13.1 9 / 5
1.13.0 9 / 5
1.12.0 9 / 5
1.11.1 9 / 5
1.11.0 9 / 5
1.10.1 9 / 5
1.10.0 9 / 5
1.9.0 9 / 5
1.8.1 9 / 5
1.8.0 9 / 5
1.7.0 9 / 5
1.6.0 9 / 5
1.5.1 9 / 5
1.5.0 9 / 5
1.4.0 9 / 5
1.2.0 8 / 5
1.1.0 8 / 5
1.0.3 8 / 5
1.0.2 8 / 5
1.0.1 8 / 5
1.0.0 8 / 5

v1.15.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.15.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.14.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: notrab → lightwalker_eth (on 2026-03-04, known maintainer) provenance

This version was published by a different npm account (lightwalker_eth) than the most recent previously approved version (notrab) on 2026-03-04, but lightwalker_eth 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.

v1.5.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: notrab → lightwalker_eth (on 2026-01-17, known maintainer) provenance

This version was published by a different npm account (lightwalker_eth) than the most recent previously approved version (notrab) on 2026-01-17, but lightwalker_eth 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.

v1.5.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: notrab → lightwalker_eth (on 2026-01-14, known maintainer) provenance

This version was published by a different npm account (lightwalker_eth) than the most recent previously approved version (notrab) on 2026-01-14, but lightwalker_eth 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.

v1.4.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: notrab → lightwalker_eth (on 2026-01-12, known maintainer) provenance

This version was published by a different npm account (lightwalker_eth) than the most recent previously approved version (notrab) on 2026-01-12, but lightwalker_eth 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.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.