Apollo is marked deprecated. Use this guide to understand its former purpose, verify replacement guidance, and avoid starting a new dependency without a migration plan.
Quick verdict
[2022-01-21] Note - Upcoming Deprecation Plans: We (Apollo) are working towards fully deprecating this repository and its related projects. Most of the functionality in this repository has been replaced by newer projects and the rest will be soon. We'll share detailed migration documentation when everything here is ready to be officially deprecated, but just a heads up in case you're planning on adopting anything here for a new project (which you still can of course if the tooling here works for
Shortlist Apollo only if its documented purpose matches your use case; the source signals below are context, not an endorsement.
Best fit — and when to skip it
Apollo is most relevant to developers working with JavaScript/TypeScript. It belongs on a shortlist when that stated purpose matches a concrete requirement.
Skip or postpone it when the documented runtime, license, dependency footprint, or maintenance model conflicts with your project. Popularity alone is not a reason to migrate.
Setup and first checks
Confirm the exact package name, current version, runtime requirement, dependencies, provenance, and release notes before installing apollo in a production project. Start in a disposable example and exercise the use case you actually need.
Maintenance and risk signals
The collected source record shows 145.3K weekly downloads, version 2.34.0, and released 2022-05-20.
The recorded Node.js requirement is >=8.
The current package metadata lists 37 direct dependencies.
The registry lists 1 maintainers.
The source reports the MIT license.
The latest npm version is marked deprecated: The `apollo` package is deprecated and no longer maintained. It has been replaced by the Apollo Rover CLI (`@apollo/rover`) — see the migration guide at https://go.apollo.dev/t/mig
Registry downloads include automated requests and are not unique users, satisfaction, or proof of quality.
Bottom line
Apollo is worth a closer look when its stated purpose and ecosystem fit your project. Compare it with related tools, verify the current documentation, and test the smallest realistic use case before committing.
Try it safely
npm install apolloUse the official npm package page to confirm the current version, documentation, dependencies, provenance, and compatibility requirements before installing it in an important project.
At a glance
Weekly downloads measure registry requests, including automated installs. They are not GitHub star growth and do not represent unique users.
Sources and methodology
This guide uses public records collected on 2026-08-07. Source completeness is High; this label is not a product rating.
View the supporting source data
- Node.js engine: >=8 — official record
- Official package summary: [2022-01-21] Note - Upcoming Deprecation Plans: We (Apollo) are working towards fully deprecating this repository and its related projects. Most of the functionality in this repository has been replaced by newer projects and the rest will be soon. We'll share detailed migration documentation when everything here is ready to be officially deprecated, but just a heads up in case you're planning on adopting anything here for a new project (which you still can of course if the tooling here works for — official record
- Maintainers listed: 1 — official record
- Registry modified: 2026-07-03 — official record
- Direct dependencies: 37 — official record
- License: MIT — official record
- Package: apollo — official record
- Download window: 2026-07-30 to 2026-08-05 — official record
- Weekly downloads: 145.3k — official record
- Latest version: 2.34.0 — official record
- Latest version published: 2022-05-20 — official record
Evidence limitations
- The latest npm version is marked deprecated: The `apollo` package is deprecated and no longer maintained. It has been replaced by the Apollo Rover CLI (`@apollo/rover`) — see the migration guide at https://go.apollo.dev/t/mig
- Official metadata was collected as source evidence; no independent installation, benchmark, security audit, or practical product evaluation is claimed.
Data note: This automated workflow updated the guide on 2026-08-07 from public NPM package records. Metrics can change after collection. No independent product testing or endorsement is claimed.