dead-deps — what happened to your dependencies

Is apollo-server still maintained?

No — apollo-server stopped being maintained around November 2023. The same project continues under the name @apollo/server.

Status
No longer maintained
Last maintained
November 2023
Use instead
@apollo/server on npm
Succession
Renamed package
Drop-in
no — expect code changes
Confidence
high

What should I use instead of apollo-server?

The same project continues under the name @apollo/server. @apollo/server is not a drop-in replacement, so expect to change call sites.

How to migrate from apollo-server to @apollo/server

Replace it with @apollo/server plus startStandaloneServer(server, {listen: {port: 4000}}) from @apollo/server/standalone, which is the equivalent of the old server.listen() convenience API.

Why apollo-server is on this list

apollo-server was the batteries-included entry point for Apollo Server v2 and v3, both of which Apollo has declared end-of-life. The npm notice directs users to the @apollo/server package, the same project published under the Apollo scope. The final release under the old name was 3.13.0 in November 2023, and Apollo Server 5 is the currently supported line.

The succession is settled: primary sources agree and the ecosystem has already moved.

apollo-server alternatives

Beyond the primary recommendation, these are credible for apollo-server's use case:

Check your own project for apollo-server

npx dead-deps --all --min-state unmaintained

Run that in the directory holding your lockfile. If apollo-server is anywhere in your tree — a direct dependency or buried under something else — it appears in the report with this verdict, this successor and the same evidence links, alongside anything else that has stopped moving. Nothing is uploaded; the scan reads your lockfile locally and queries public registry metadata.

Exit code 1 means something was flagged, which makes npx dead-deps --min-state deprecated usable as a CI gate. See how verdicts are produced.

Evidence

Every claim on this page traces to a primary source. Check them:

See the full index of covered packages, or read the methodology for how a verdict is reached and why a quiet package is not a dead one.