@graphql-hive/router-runtime
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Scoped package from established org; missing description is cosmetic, not a malware signal. | ai | |
| phantom-deps | phantom-dep:@graphql-hive/router-query-planner | AI (phantom-deps): Same-org sibling package; likely re-exported rather than directly imported in source. | ai | |
| dependencies | unvetted-dep:@graphql-tools/federation | AI (dependencies): The Guild ecosystem package; same trusted publisher org as this package. | ai | |
| dependencies | unvetted-dep:@graphql-mesh/fusion-runtime | AI (dependencies): The Guild ecosystem package; same trusted publisher org as this package. | ai | |
| dependencies | unvetted-dep:@graphql-mesh/transport-common | AI (dependencies): The Guild ecosystem package; same trusted publisher org as this package. | ai | |
| dependencies | unvetted-dep:@graphql-hive/router-query-planner | AI (dependencies): Sibling package in the same @graphql-hive org; same trusted publisher. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.4.10 | 11 / 2 | |
| 1.4.9 | 11 / 2 | |
| 1.4.8 | 11 / 2 | |
| 1.4.7 | 11 / 2 | |
| 1.4.6 | 11 / 2 | |
| 1.4.5 | 11 / 2 | |
| 1.4.4 | 11 / 2 | |
| 1.3.1 | 11 / 2 | |
| 1.3.0 | 11 / 2 | |
| 1.2.4 | 9 / 2 | |
| 1.2.1 | 9 / 2 | |
| 1.2.0 | 9 / 2 | |
| 1.1.16 | 9 / 2 | |
| 1.1.15 | 9 / 2 | |
| 1.1.14 | 9 / 2 | |
| 1.1.13 | 9 / 2 | |
| 1.1.12 | 9 / 2 | |
| 1.1.11 | 9 / 2 | |
| 1.1.10 | 9 / 2 | |
| 1.1.9 | 9 / 2 | |
| 1.1.8 | 9 / 2 | |
| 1.1.7 | 9 / 2 | |
| 1.1.6 | 9 / 2 | |
| 1.1.5 | 9 / 2 | |
| 1.1.4 | 9 / 2 | |
| 1.1.3 | 9 / 2 | |
| 1.1.2 | 9 / 2 | |
| 1.1.1 | 9 / 2 | |
| 1.1.0 | 9 / 2 | |
| 1.0.1 | 9 / 2 | |
| 1.0.0 | 9 / 2 |
v1.4.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.