Is chalk healthy, maintained, and safe?
Mostly yes — chalk is maintained, with a couple of watch-items rather than red flags.
The verdict
chalk earns a health score of 77/100, a low risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Mostly yes — chalk is maintained, with a couple of watch-items rather than red flags.
Its most recent release shipped on 26 July 2026 — 2 days ago — so development is clearly active. Across 45 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. Ownership rests on a single maintainer — a bus-factor of one, meaning one person's availability is a single point of failure for everyone downstream.
OSV lists 1 known advisory for chalk, of assorted severity. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.
A couple of watch-items aside, chalk is a reasonable dependency to rely on; keep an eye on the flagged signals. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (1)
Malicious code in chalk (npm)
Key facts
- Latest version
- v6.0.0
- Last release
- 26 July 2026 (2 days ago)
- Total releases
- 45
- First release
- 3 August 2013
- Package age
- 13.0 years
- Maintainers
- 1
- Known advisories
- 1
- Confidence
- High
Frequently asked
Is chalk still maintained?
Yes — chalk released as recently as 26 July 2026 (2 days ago), so it is actively maintained.
Does chalk have known security vulnerabilities?
Yes — OSV lists 1 advisory for chalk. See the advisory list on this page for the OSV/GHSA identifiers.
Is chalk safe to use?
Mostly yes — chalk is maintained, with a couple of watch-items rather than red flags. OSPulse rates it 77/100 (low risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
chalk is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-28 · scores are deterministic and recomputed on each refresh.