Is hapi still maintained?
No — hapi stopped being maintained around February 2019. The same project continues under the name @hapi/hapi.
- Status
- No longer maintained
- Last maintained
- February 2019
- Use instead
@hapi/hapi— on npm- Succession
- Renamed package
- Drop-in
- no — expect code changes
- Confidence
- high
What should I use instead of hapi?
The same project continues under the name @hapi/hapi. @hapi/hapi is not a drop-in replacement, so expect to change call sites.
How to migrate from hapi to @hapi/hapi
Change the dependency to @hapi/hapi and update every require('hapi') to require('@hapi/hapi'); plugins moved to the same scope, so inert, vision and bell become @hapi/inert, @hapi/vision and @hapi/bell. Expect breaking changes between v18 and v21 beyond the rename.
Why hapi is on this list
The hapi framework moved to the @hapi npm scope, and the unscoped hapi package stopped at 18.1.0 in February 2019. Its npm notice warns that the version has known security issues and defects and asks users to upgrade to @hapi/hapi or take a commercial license, which the maintainers offered for v16 through v19. Only @hapi/hapi v20 and later receive open source security fixes.
The succession is settled: primary sources agree and the ecosystem has already moved.
hapi alternatives
Beyond the primary recommendation, these are credible for hapi's use case:
fastify— view on npmexpress— view on npmkoa— view on npm
Check your own project for hapi
npx dead-deps --all --min-state unmaintainedRun that in the directory holding your lockfile. If hapi 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:
- npm deprecation notice for hapinpmjs.com
- Maintainer statement on support and commercial licensing for hapi v16-v19github.com
Packages related to hapi
- @hapi/joiRenamed package: joi · unmaintained since March 2020
- feathersRenamed package: @feathersjs/feathers · unmaintained since January 2018
- labRenamed package: @hapi/lab · unmaintained since February 2019
- react-testing-libraryRenamed package: @testing-library/react · unmaintained since May 2019
- wreckRenamed package: @hapi/wreck · unmaintained since March 2019
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.