dead-deps — what happened to your dependencies

Is wreck still maintained?

No — wreck stopped being maintained around March 2019. The same project continues under the name @hapi/wreck.

Status
No longer maintained
Last maintained
March 2019
Use instead
@hapi/wreck — on npm
Succession
Renamed package
Drop-in
no — expect code changes
Confidence
high

What should I use instead of wreck?

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

How to migrate from wreck to @hapi/wreck

Install @hapi/wreck and update the require path; if you are not otherwise using hapi, undici or got are better-supported general-purpose clients.

Why wreck is on this list

wreck is hapi's HTTP client utility and moved to the @hapi scope along with the rest of the framework. The unscoped package stopped at 14.2.0 in March 2019 and its npm notice says the module has moved to @hapi/wreck and is no longer maintained under the old name. The scoped package is still being released.

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

wreck alternatives

Beyond the primary recommendation, these are credible for wreck's use case:

Check your own project for wreck

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

Run that in the directory holding your lockfile. If wreck 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.