← Home

@graphprotocol/interfaces

Contract interfaces for The Graph protocol

4
Versions
GPL-2.0-or-later
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

nasmrneysofua3k5fordnluttertmigonejuanmardefagodnfodjotheoduscmwhitedmigueldeeliasandras_enpcarranzav_edgeandnodemitchhs12dwerner-enlnsdedge-and-nodenomativyaroshkvoretspdiogo-tgfbairunnikgrafbenface.com

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Diff spans 20+ unimported versions; likely routine org maintainer rotation, not compromise. ai
maintainer-change maintainer-removed AI (maintainer-change): Paired with addition across long version gap; consistent with normal handoff. ai
source-diff large-new-source-files AI (source-diff): Diff baseline is v0.1.0; build artifacts scale with contract/type generation, not injected code. ai

Versions (showing 4 of 4)

Version Deps Published
0.6.6 0 / 18
0.6.5 0 / 18
0.6.4 0 / 18
0.1.0 0 / 8

v0.6.5

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: tmigone → migueldeelias (on 2025-12-14, known maintainer) provenance

This version was published by a different npm account (migueldeelias) than the most recent previously approved version (tmigone) on 2025-12-14, but migueldeelias 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.

v0.6.4

1 finding
LOW No provenance attestation provenance

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