VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

lit: vulnerability history, versions and safety

lit 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 lit vulnerabilities

Vulert verdict on lit 3.3.3 i

Updated on 23 Oct 2026

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

Package health score 89/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 3.3.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 22,962 packages i
  • Stars 21,851 i
  • OpenSSF scorecard 6/10 i
  • Last release 5 months ago i
  • Licence BSD-3-Clause 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 lit, 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
3.3.3 14 May 2026 none BSD-3-Clause — Details →
3.3.2 23 Dec 2025 none BSD-3-Clause — Details →
3.3.1 11 Jul 2025 none BSD-3-Clause — Details →
3.3.0 11 Apr 2025 none BSD-3-Clause — Details →
3.2.1 07 Oct 2024 none BSD-3-Clause — Details →
3.2.0 05 Aug 2024 none BSD-3-Clause — Details →
3.1.4 04 Jun 2024 none BSD-3-Clause — Details →
3.1.3 15 Apr 2024 none BSD-3-Clause — Details →
3.1.2 31 Jan 2024 none BSD-3-Clause — Details →
3.1.1 09 Jan 2024 none BSD-3-Clause — Details →
3.1.0 16 Nov 2023 none BSD-3-Clause — Details →
3.0.2 02 Nov 2023 none BSD-3-Clause — Details →
3.0.1 28 Oct 2023 none BSD-3-Clause — Details →
3.0.0 10 Oct 2023 none BSD-3-Clause — Details →
3.0.0-pre.1 29 Sep 2023 none BSD-3-Clause — Details →
2.8.0 02 Aug 2023 none BSD-3-Clause — Details →
2.7.6 05 Jul 2023 none BSD-3-Clause — Details →
2.7.5 01 Jun 2023 none BSD-3-Clause — Details →
2.7.4 04 May 2023 none BSD-3-Clause — Details →
3.0.0-pre.0 27 Apr 2023 none BSD-3-Clause — Details →
2.7.3 26 Apr 2023 none BSD-3-Clause — Details →
2.7.2 05 Apr 2023 none BSD-3-Clause — Details →
2.7.1 03 Apr 2023 none BSD-3-Clause — Details →
2.7.0 22 Mar 2023 none BSD-3-Clause — Details →
2.6.1 12 Jan 2023 none BSD-3-Clause — Details →
2.6.0 09 Jan 2023 none BSD-3-Clause — Details →
2.5.0 08 Dec 2022 none BSD-3-Clause — Details →
2.4.1 03 Nov 2022 none BSD-3-Clause — Details →
2.4.0 05 Oct 2022 none BSD-3-Clause — Details →
2.3.1 18 Aug 2022 none BSD-3-Clause — Details →
2.3.0 12 Aug 2022 none BSD-3-Clause — Details →
2.3.0-next.1 25 Jul 2022 none BSD-3-Clause — Details →
2.3.0-next.0 25 Jul 2022 none BSD-3-Clause — Details →
2.2.8 22 Jul 2022 none BSD-3-Clause — Details →
2.2.7 29 Jun 2022 none BSD-3-Clause — Details →
2.2.6 14 Jun 2022 none BSD-3-Clause — Details →
2.2.5 25 May 2022 none BSD-3-Clause — Details →
2.2.4 17 May 2022 none BSD-3-Clause — Details →
2.2.3 29 Apr 2022 none BSD-3-Clause — Details →
2.2.2 06 Apr 2022 none BSD-3-Clause — Details →
2.2.1 15 Mar 2022 none BSD-3-Clause — Details →
2.2.0 18 Feb 2022 none BSD-3-Clause — Details →
2.1.4 15 Feb 2022 none BSD-3-Clause — Details →
2.1.3 07 Feb 2022 none BSD-3-Clause — Details →
2.1.2 25 Jan 2022 none BSD-3-Clause — Details →
2.1.1 06 Jan 2022 none BSD-3-Clause — Details →
2.1.0 05 Jan 2022 none BSD-3-Clause — Details →
2.0.2 08 Oct 2021 none BSD-3-Clause — Details →
2.0.1 07 Oct 2021 none BSD-3-Clause — Details →
2.0.0 21 Sep 2021 none BSD-3-Clause — Details →
2.0.0-rc.4 03 Sep 2021 none BSD-3-Clause — Details →
2.0.0-rc.3 19 Aug 2021 none BSD-3-Clause — Details →
2.0.0-rc.2 07 May 2021 none BSD-3-Clause — Details →
2.0.0-rc.1 21 Apr 2021 none BSD-3-Clause — Details →
2.0.0-pre.2 31 Mar 2021 none BSD-3-Clause — Details →
2.0.0-pre.1 12 Feb 2021 none BSD-3-Clause — Details →
1.0.1 05 Jul 2012 none MIT — Details →
1.0.0 04 Jul 2012 none MIT — Details →

All 58 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 lit

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 lit

Is lit safe to use?

Vulert has no vulnerabilities on record for lit 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 lit's Vulert package health score?

Vulert scores lit 89/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 lit affected?

No. 3.3.3, 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 lit should I use?

3.3.3 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 lit have?

0 vulnerabilities are recorded for lit 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 lit vulnerabilities disclosed?

0 vulnerabilities were recorded for lit 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 lit 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 lit for upcoming vulnerabilities?

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