← Home

@graphql-codegen/fragment-matcher

npm Repository
4
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

dotansimhaardatankamilkisielaurigotheguild-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from theguild-bot to GitHub Actions CI; SLSA provenance confirms legitimate publish pipeline. ai
provenance missing-githead AI (provenance): gitHead omission is expected when publishing via GitHub Actions with npm provenance. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a declared dep used implicitly by TypeScript-compiled output. ai

Versions (showing 4 of 4)

Version Deps Published
7.0.1 2 / 0
7.0.0 2 / 0
6.0.1 2 / 0
6.0.0 2 / 0

v7.0.1

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

HIGH Publisher changed: theguild-bot → GitHub Actions (on 2026-05-27) provenance

This version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v7.0.0

1 finding
LOW No provenance attestation provenance

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

v6.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.