dead-deps — what happened to your dependencies

Is jscs still maintained?

No — jscs stopped being maintained around April 2016. jscs's own maintainers named eslint as the successor.

Status
No longer maintained
Last maintained
April 2016
Use instead
eslint on npm
Succession
Successor named by the maintainers
Drop-in
no — expect code changes
Confidence
high

What should I use instead of jscs?

jscs's own maintainers named eslint as the successor. eslint is not a drop-in replacement, so expect to change call sites.

How to migrate from jscs to eslint

Start from a fresh eslint --init config rather than a mechanical translation, and delegate formatting rules to Prettier; there is no maintained .jscsrc converter.

Why jscs is on this list

JSCS merged into ESLint in 2016: the JSCS maintainers joined the ESLint project and the two linters were consolidated into one. The npm package's last release was 3.0.7 in July 2016 and it is deprecated with a notice linking to the maintainer's announcement; the repository is described as unmaintained and was archived in March 2024. ESLint has since moved formatting rules out of core, so Prettier or @stylistic now covers the purely stylistic part of what JSCS did.

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

jscs alternatives

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

Check your own project for jscs

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

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