dead-deps — what happened to your dependencies

Is hermione still maintained?

No — hermione stopped being maintained around June 2024. The same project continues under the name testplane.

Status
No longer maintained
Last maintained
June 2024
Use instead
testplane on npm
Succession
Renamed package
Drop-in
yes — swap the import
Confidence
high

What should I use instead of hermione?

The same project continues under the name testplane. testplane is close enough to a drop-in replacement that most projects only change the dependency and the import.

How to migrate from hermione to testplane

Replace the hermione dependency with testplane at the same major version and rename .hermione.conf.js to .testplane.conf.js; the official upgrade guide on testplane.io covers the renamed CLI flags.

Why hermione is on this list

Hermione was renamed to Testplane in 2024 by the same gemini-testing team after copyright and trademark issues with the old name; the repository was renamed too, so github.com/gemini-testing/hermione now resolves to the Testplane repository. The hermione README states the project has been renamed and is backward compatible, and the Testplane README states that Testplane v8.x is a drop-in replacement for Hermione v8.x. The hermione package stopped receiving releases after 8.9.6 in June 2024 while Testplane continued the same version line.

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

hermione alternatives

The dataset lists no second option: testplane is where the ecosystem went, and nothing else has meaningful adoption.

Check your own project for hermione

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

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