@graphql-tools/federation
Useful tools to create and manipulate GraphQL schemas.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit dependency of TypeScript runtime; stable for this package. | ai | |
| phantom-deps | phantom-dep:@graphql-tools/wrap | AI (phantom-deps): Re-exported by federation package; implicit transitive dependency. | ai | |
| phantom-deps | phantom-dep:@graphql-tools/merge | AI (phantom-deps): Re-exported by federation package; implicit transitive dependency. | ai | |
| phantom-deps | phantom-dep:@graphql-tools/schema | AI (phantom-deps): Re-exported by federation package; implicit transitive dependency. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 4.4.5 | 14 / 11 | |
| 4.4.4 | 14 / 11 | |
| 4.4.3 | 14 / 11 | |
| 4.4.2 | 14 / 11 | |
| 4.4.1 | 14 / 11 | |
| 4.4.0 | 14 / 11 | |
| 4.3.7 | 14 / 9 | |
| 4.3.6 | 14 / 9 | |
| 4.3.5 | 14 / 9 | |
| 4.3.4 | 14 / 9 | |
| 4.3.3 | 14 / 9 | |
| 4.3.2 | 14 / 9 | |
| 4.3.1 | 14 / 9 | |
| 4.3.0 | 14 / 9 | |
| 4.2.14 | 14 / 9 | |
| 4.2.13 | 14 / 9 | |
| 4.2.12 | 14 / 9 | |
| 4.2.11 | 14 / 9 | |
| 4.2.10 | 14 / 9 | |
| 4.2.9 | 14 / 8 | |
| 4.2.8 | 14 / 8 | |
| 4.2.7 | 14 / 8 | |
| 4.2.6 | 14 / 8 | |
| 4.2.5 | 14 / 8 | |
| 4.2.4 | 14 / 8 | |
| 4.2.3 | 14 / 8 | |
| 4.2.2 | 14 / 8 | |
| 4.2.1 | 14 / 8 | |
| 4.2.0 | 14 / 8 | |
| 4.1.0 | 14 / 8 | |
| 4.0.5 | 14 / 8 | |
| 4.0.4 | 14 / 8 | |
| 4.0.3 | 14 / 8 | |
| 4.0.2 | 14 / 8 | |
| 4.0.1 | 14 / 8 | |
| 4.0.0 | 14 / 8 |
v4.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.