apollographql/apollo-tooling

✏️ Apollo CLI for client tooling (Mostly replaced by Rover)

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 22nd, 2026
Created on August 12th, 2016
Open Issues & Pull Requests: 364 (+0)
GitHub issues: Enabled
Number of forks: 460
Total Stargazers: 3,041 (+0)
Total Subscribers: 57 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 37.5 days
Mean response time: 497.9 days
90th percentile: 2233.4 days
Tracked items: 14

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 2,274 days
Stale 30+ days: 7
Stale 90+ days: 7

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • :tada: feature (4)
  • :hammer: cli (3)
  • :x: errors (3)
  • 🤖 component - codegen (3)
  • :spiral_notepad: component - vscode (2)
  • :1st_place_medal: good-first-issue (1)
  • :bird: component - swift (1)
  • 🙏 help-wanted (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Apollo CLI is a command-line tool for GraphQL client and server development that validates schemas, lints operations, and generates static types.

The tool addresses the need to keep GraphQL clients and servers in sync by providing validation and code generation capabilities. It allows developers to check client operations against a server schema, download schemas for local use, and generate TypeScript types from GraphQL queries to improve type safety on the client side. The approach centers on integrating schema validation and type generation into the development workflow through command-line commands that interact with GraphQL registries and local schema files.

New projects should not adopt this tool. The README explicitly recommends using graphql-code-generator instead for code generation, which is the primary capability most developers would seek from this package. The service-related commands have reached end-of-life, and the project maintainers have announced plans to fully deprecate the repository, with most functionality already replaced by newer projects. Existing projects using the tool can continue to do so with minimal support, but migration to successor tools is the recommended path forward.

Development on the project has entered a maintenance-only phase with minimal activity. The codebase remains in TypeScript but receives only housekeeping updates, such as the relocation of the GraphQL VSCode extension to a separate repository. No active feature development or bug fixes are being prioritized as the team focuses on deprecation planning and directing users toward replacement tools.