Skip to content

Missing provenance attestation in recent releases causing trust downgrade errors #2959

Open

Description

@patrickZhengIT

Hi,

We're encountering trust downgrade errors when using the latest version(4.4.0). Our build uses pnpm with strict trust policy checks enabled, and we're seeing failures because latest versions lack provenance attestation.

Affected packages:

@graphql-tools/executor-http@1.3.3
@graphql-tools/executor-graphql-ws@2.0.7
@graphql-tools/wrap@10.1.4

Error example:

ERR_PNPM_TRUST_DOWNGRADE High-risk trust downgrade for "@graphql-tools/executor-http@1.3.3" (possible package takeover)

Context:

Latest version of @graphql-eslint/eslint-plugin depends on these packages. When we try to upgrade other packages, this will trigger pnpm's trust downgrade protection, which blocks installation as a security precaution.

We've temporarily worked around this by excluding these specific versions from trust checks, but it would be great to have provenance restored in future releases for better supply chain security.

I already request this to be fixed in gateway, the way to fix may be similar.

Questions:

Can future releases include provenance attestation (For example: via npm publish --provenance from GitHub Actions)?
Could this fixed in next version?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      ⌂ 换网址