color-convertnpm

Verdict

Quiet, but healthy

color-convert has been quiet — no commits for 10 months, but nothing suggests trouble: 5 of 14 open issues have had no reply. This is a settled project, not a stalled one.

health 56/100

Why this verdict?

coasting — No commits for 90–365 days, with nothing else deteriorating.

last commit 293 days ago

Judged yesterday from signal heuristics. How each verdict is decided

latest 3.1.3
licence MIT
stars 824
checked yesterday
registry ↗
repository ↗

Signals · last 1 check

Commits 90d

Open issues

Unanswered

Contributors

State history 1

When	Change
2026-09-03	first verdict: coasting

Supply-chain history 1

account hijacked 2025-09

Its maintainer was phished and versions with a crypto-clipboard payload were live for a few hours, in the same incident across several packages from one account.

Malicious versions were removed within hours; the exposure window was short.

Source: npm phishing incident reporting, 8 September 2025. History, not a warning about today — the verdict above is about maintenance now.

Badge

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/npm/color-convert.svg)](https://isitdeadyet.dev/npm/color-convert)

Watch it

Get told when color-convert changes state, changes licence, or is deprecated — instead of finding out during an incident.

Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.