Is tslint healthy, maintained, and safe?
Probably not. tslint has gone quiet for over two years and shows the hallmarks of an abandoned package.
The verdict
On the OSPulse health scale, tslint lands at 25/100, a high risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Probably not. tslint has gone quiet for over two years and shows the hallmarks of an abandoned package.
The last sign of life was 31 July 2020, more than 6 years ago (2237 days). By any practical measure the package looks abandoned. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. 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.
On the security side, OSV has no advisories on record for tslint today. That's reassuring, but "no known advisory" is not the same as "no vulnerability". It only means nothing has been disclosed and indexed yet.
Treat tslint as a liability to manage: review the evidence above, pin or patch, and evaluate alternatives. 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
Key facts
- Latest version
- v6.1.3
- Last release
- 31 July 2020 (2237 days ago)
- Total releases
- 182
- First release
- 28 July 2013
- Package age
- 13.1 years
- Maintainers
- 1
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is tslint still maintained?
It doesn't appear to be. The last release was 31 July 2020, over two years ago, which usually indicates an abandoned package.
Does tslint have known security vulnerabilities?
No advisories are currently recorded for tslint in the OSV database. That means none have been publicly disclosed and indexed, so it is not a guarantee of safety.
Is tslint safe to use?
Probably not. tslint has gone quiet for over two years and shows the hallmarks of an abandoned package. OSPulse rates it 25/100 (high risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
tslint 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-09-15 · scores are deterministic and recomputed on each refresh.