Repo brief: graphile/crystal

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T11:44:20.032Z · commit 7914f441356e

Verdict

Healthy — Healthy across all four use cases

• Last commit 6d ago
• 5 active contributors
• MIT licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

Graphile Crystal is a monorepo containing Grafast (a planning and execution engine for GraphQL.js) and PostGraphile (an auto-generated GraphQL API generator backed by PostgreSQL). The core innovation is replacing traditional GraphQL resolvers with declarative "plan resolvers" that analyze the entire request upfront, allowing the engine to batch queries, eliminate N+1 problems, and execute with minimal server overhead. Monorepo structure with packages organized under grafast/ including core engine, dataplan-pg (PostgreSQL plan classes), dataplan-json (JSON encoding/decoding), and codegen-plugin (GraphQL code generator plugin). Each package is independently versioned with its own…

Start here

Open these first:

• grafast/grafast/src — Core Grafast planning and execution engine implementation; the foundational layer for all GraphQL plan resolvers.
• grafast/dataplan-pg/src/index.ts — PostgreSQL data plan entry point integrating pg-specific steps and codecs into the Grafast pipeline.
• grafast/dataplan-pg/src/executor.ts — Executes PostgreSQL queries within Grafast's execution model; critical for data retrieval and transaction handling.
• grafast/dataplan-pg/src/steps/pgSelect.ts — Primary step for building parameterized SQL SELECT queries; demonstrates the plan-resolver pattern.
• grafast/grafast/package.json — Defines Grafast's public API surface, export points, and peer dependencies for GraphQL integration.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone the repository with git clone https://github.com/graphile/crystal.git and cd crystal. Based on presence of TypeScript tsconfig.json files and yarn script references in package.json, install dependencies with…

Daily commands:

From repository root, run yarn build to compile TypeScript across all packages (per grafast/codegen-plugin/package.json and individual tsconfig files). For package-specific execution, enter the target package direct…

…shortened for this brief.

Key cautions & unknowns

• Single-maintainer risk — top contributor 86% of recent commits
• Node version requirement is strict: engines.node specifies >=22, meaning older Node versions will fail—verify your local and deployment Node versions before starting. Monorepo workspace dependencies: packages…
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.