← Home

babel-plugin-relay

A Babel Plugin for use with Relay applications.

5
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

zpaofbyuzhijosephsavonarelay-bot

Keywords

graphqlrelaybabelbabel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from relay-bot to GitHub Actions CI/CD is confirmed legitimate by SLSA provenance attestation from facebook/relay. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer cleanup consistent with Meta's shift to automated CI/CD publishing; SLSA attestation confirms repo integrity. ai
publish-pattern rapid-publish AI (publish-pattern): Rapid publish is expected from automated CI/CD pipelines; SLSA attestation confirms legitimate origin. ai

Versions (showing 5 of 5)

Version Deps Published
21.0.1 3 / 3
21.0.0 3 / 3
20.1.1 3 / 3
20.1.0 3 / 3
20.0.0 3 / 3

v21.0.1

1 finding
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.

v21.0.0

2 findings
HIGH Publisher changed: relay-bot → GitHub Actions (on 2026-05-18) provenance

This version was published by a different npm account than previous versions on 2026-05-18. 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.

v20.1.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.

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