@contractspec/lib.graphql-federation
Pothos federation helpers and subgraph schema export utilities
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@pothos/plugin-directives | AI (dependencies): Legitimate Pothos GraphQL ecosystem plugin; stable dependency for this federation helper package. | ai | |
| dependencies | unvetted-dep:@pothos/plugin-federation | AI (dependencies): Legitimate Pothos GraphQL ecosystem plugin; core dependency for this federation helper package. | ai | |
| provenance | no-provenance | AI (provenance): Org-internal package; no provenance is consistent across all 83 versions and poses no security risk here. | ai | |
| phantom-deps | phantom-dep:@apollo/subgraph | AI (phantom-deps): Apollo subgraph is a declared runtime dep used via config/re-export pattern in a federation library; not a direct import. | ai | |
| phantom-deps | phantom-dep:@pothos/plugin-directives | AI (phantom-deps): Pothos plugin-directives used via config/plugin registration pattern; phantom-dep false positive for this package. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 3.7.22 | 6 / 3 | |
| 3.7.21 | 6 / 3 | |
| 3.7.20 | 6 / 3 | |
| 3.7.19 | 6 / 3 | |
| 3.7.18 | 6 / 3 | |
| 3.7.17 | 6 / 3 | |
| 3.7.16 | 6 / 3 | |
| 3.7.15 | 6 / 3 | |
| 3.7.14 | 6 / 3 | |
| 3.7.13 | 5 / 3 | |
| 3.7.12 | 5 / 3 | |
| 3.7.11 | 5 / 3 | |
| 3.7.10 | 5 / 3 | |
| 3.7.9 | 5 / 3 | |
| 3.7.8 | 5 / 3 | |
| 3.7.6 | 5 / 3 | |
| 3.7.5 | 5 / 3 | |
| 3.7.4 | 5 / 3 | |
| 3.7.3 | 5 / 3 | |
| 3.7.1 | 5 / 3 | |
| 3.7.0 | 5 / 3 | |
| 3.6.0 | 5 / 3 | |
| 3.5.5 | 5 / 3 | |
| 3.5.4 | 5 / 3 | |
| 3.5.3 | 5 / 3 | |
| 3.5.2 | 5 / 3 | |
| 3.5.0 | 5 / 3 | |
| 3.4.3 | 5 / 3 | |
| 3.4.2 | 5 / 3 | |
| 3.4.1 | 5 / 3 | |
| 3.4.0 | 5 / 3 | |
| 3.3.0 | 5 / 3 | |
| 3.2.0 | 5 / 3 | |
| 3.1.0 | 5 / 3 | |
| 3.0.0 | 5 / 3 | |
| 2.9.0 | 5 / 3 | |
| 2.8.0 | 5 / 3 | |
| 2.7.0 | 5 / 3 | |
| 2.6.0 | 5 / 3 | |
| 2.5.0 | 5 / 3 | |
| 2.4.0 | 5 / 3 | |
| 2.3.0 | 5 / 3 | |
| 2.2.0 | 5 / 3 | |
| 2.1.0 | 5 / 3 | |
| 2.0.0 | 5 / 3 | |
| 1.62.0 | 5 / 3 | |
| 1.61.0 | 5 / 3 | |
| 1.60.0 | 5 / 3 | |
| 1.59.0 | 5 / 3 | |
| 1.58.0 | 5 / 3 | |
| 1.57.0 | 5 / 4 |
v3.7.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.