VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

tslib: vulnerability history, versions and safety

tslib is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all tslib vulnerabilities

Vulert verdict on tslib 2.8.1 i

Updated on 23 Oct 2026

Good news: 2.8.1, the version you would install today, has no known vulnerabilities.

Package health score 85/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on 2.8.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.8.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.8.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1,620,836 packages i
  • Stars 111,552 i
  • OpenSSF scorecard 7/10 i
  • Last release 23 months ago i
  • Licence 0BSD i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for tslib, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.8.1 31 Oct 2024 none 0BSD — Details →
2.8.0 15 Oct 2024 none 0BSD — Details →
2.7.0 23 Aug 2024 none 0BSD — Details →
2.6.3 04 Jun 2024 none 0BSD — Details →
2.6.2 18 Aug 2023 none 0BSD — Details →
2.6.1 24 Jul 2023 none 0BSD — Details →
2.6.0 26 Jun 2023 none 0BSD — Details →
2.5.3 02 Jun 2023 none 0BSD — Details →
2.5.2 18 May 2023 none 0BSD — Details →
2.5.1 17 May 2023 none 0BSD — Details →
2.5.0 26 Jan 2023 none 0BSD — Details →
2.4.1 31 Oct 2022 none 0BSD — Details →
2.4.0 22 Apr 2022 none 0BSD — Details →
2.3.1 11 Aug 2021 none 0BSD — Details →
2.3.0 11 Jun 2021 none 0BSD — Details →
2.2.0 05 Apr 2021 none 0BSD — Details →
2.1.0 05 Jan 2021 none 0BSD — Details →
2.0.3 09 Oct 2020 none 0BSD — Details →
1.14.1 09 Oct 2020 none 0BSD — Details →
2.0.2 06 Oct 2020 none 0BSD — Details →
1.14.0 06 Oct 2020 none 0BSD — Details →
2.0.1 06 Aug 2020 none 0BSD — Details →
2.0.0 13 May 2020 none 0BSD — Details →
1.13.0 13 May 2020 none 0BSD — Details →
1.12.0 12 May 2020 none 0BSD — Details →
1.11.2 05 May 2020 none 0BSD — Details →
1.11.1 27 Feb 2020 none Apache-2.0 — Details →
1.11.0 20 Feb 2020 none Apache-2.0 — Details →
1.10.0 10 Jun 2019 none Apache-2.0 — Details →
1.9.3 22 Jun 2018 none Apache-2.0 — Details →
1.9.2 29 May 2018 none Apache-2.0 — Details →
1.9.1 14 May 2018 none Apache-2.0 — Details →
1.9.0 18 Jan 2018 none Apache-2.0 — Details →
1.8.1 06 Dec 2017 none Apache-2.0 — Details →
1.8.0 11 Oct 2017 none Apache-2.0 — Details →
1.7.1 15 May 2017 none Apache-2.0 — Details →
1.7.0 04 May 2017 none Apache-2.0 — Details →
1.6.1 19 Apr 2017 none Apache-2.0 — Details →
1.6.0 22 Feb 2017 none 0BSD — Details →
1.5.0 05 Jan 2017 none 0BSD — Details →
1.4.0 22 Dec 2016 none 0BSD — Details →
1.3.0 21 Dec 2016 none 0BSD — Details →
1.2.0 30 Nov 2016 none 0BSD — Details →
1.1.0 21 Nov 2016 none 0BSD — Details →
1.0.0 28 Jun 2016 none 0BSD — Details →
0.0.1-security 16 Jun 2016 none ISC — Details →

All 46 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for tslib

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About tslib

Is tslib safe to use?

Vulert has no vulnerabilities on record for tslib in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is tslib's Vulert package health score?

Vulert scores tslib 85/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of tslib affected?

No. 2.8.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of tslib should I use?

2.8.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does tslib have?

0 vulnerabilities are recorded for tslib in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new tslib vulnerabilities disclosed?

0 vulnerabilities were recorded for tslib in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of tslib are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor tslib for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the tslib version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.