VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

vis-timeline: vulnerability history, versions and safety

vis-timeline is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 59 releases, first recorded in Apr 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
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 vis-timeline vulnerabilities

Vulert verdict on vis-timeline 8.5.4 i

Updated on 23 Oct 2026

Good news: 8.5.4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 8.5.4 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 13 Apr 2021 i
  • Highest CVSS 6.8 i
  • With no published fix 0 i
  • Depended on by 10 packages i
  • Stars 2,570 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 months ago i
  • Licence Apache-2.0 OR MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 vis-timeline, 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
8.5.4 12 Aug 2026 none Apache-2.0 OR MIT — Details →
8.5.3 05 Aug 2026 none Apache-2.0 OR MIT — Details →
8.5.2 15 Jul 2026 none Apache-2.0 OR MIT — Details →
8.5.1 07 May 2026 none Apache-2.0 OR MIT — Details →
8.5.0 12 Dec 2025 none Apache-2.0 OR MIT — Details →
8.4.1 03 Dec 2025 none Apache-2.0 OR MIT — Details →
8.4.0 07 Nov 2025 none Apache-2.0 OR MIT — Details →
8.3.1 15 Sep 2025 none Apache-2.0 OR MIT — Details →
8.3.0 10 Aug 2025 none Apache-2.0 OR MIT — Details →
8.2.1 28 Jul 2025 none Apache-2.0 OR MIT — Details →
8.2.0 28 Jul 2025 none Apache-2.0 OR MIT — Details →
8.1.2 23 Jul 2025 none Apache-2.0 OR MIT — Details →
8.1.1 19 Jul 2025 none Apache-2.0 OR MIT — Details →
8.1.0 13 Jul 2025 none Apache-2.0 OR MIT — Details →
8.0.2 13 Jul 2025 none Apache-2.0 OR MIT — Details →
8.0.1 12 Jul 2025 none Apache-2.0 OR MIT — Details →
8.0.0 12 Jul 2025 none Apache-2.0 OR MIT — Details →
7.7.4 10 May 2025 none Apache-2.0 OR MIT — Details →
7.7.3 27 Oct 2023 none Apache-2.0 OR MIT — Details →
7.7.2 22 Mar 2023 none Apache-2.0 OR MIT — Details →
7.7.1 21 Mar 2023 none Apache-2.0 OR MIT — Details →
7.7.0 10 Jul 2022 none Apache-2.0 OR MIT — Details →
7.6.0 10 Jul 2022 none Apache-2.0 OR MIT — Details →
7.5.1 01 Mar 2022 none Apache-2.0 OR MIT — Details →
7.5.0 06 Nov 2021 none Apache-2.0 OR MIT — Details →
7.4.9 05 Jun 2021 none Apache-2.0 OR MIT — Details →
7.4.8 28 Apr 2021 none Apache-2.0 OR MIT — Details →
7.4.7 10 Apr 2021 none Apache-2.0 OR MIT — Details →
7.4.6 15 Jan 2021 none Apache-2.0 OR MIT — Details →
7.4.5 21 Dec 2020 none Apache-2.0 OR MIT — Details →
7.4.4 20 Dec 2020 none Apache-2.0 OR MIT — Details →
7.4.3 18 Dec 2020 M1 Apache-2.0 OR MIT Yes Details →
7.4.2 24 Oct 2020 M1 Apache-2.0 OR MIT Yes Details →
7.4.1 24 Oct 2020 M1 Apache-2.0 OR MIT Yes Details →
7.4.0 16 Oct 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.12 14 Oct 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.11 13 Oct 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.10 05 Oct 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.9 10 Sep 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.8 06 Sep 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.7 20 Jun 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.6 16 May 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.5 12 May 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.4 18 Mar 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.3 14 Mar 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.2 12 Mar 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.1 11 Mar 2020 M1 Apache-2.0 OR MIT Yes Details →
7.3.0 11 Mar 2020 M1 Apache-2.0 OR MIT Yes Details →
7.2.1 09 Mar 2020 M1 Apache-2.0 OR MIT Yes Details →
7.2.0 07 Mar 2020 M1 Apache-2.0 OR MIT Yes Details →
7.1.3 20 Feb 2020 M1 Apache-2.0 OR MIT Yes Details →
7.1.2 17 Feb 2020 M1 Apache-2.0 OR MIT Yes Details →
7.1.1 14 Feb 2020 M1 Apache-2.0 OR MIT Yes Details →
7.1.0 01 Feb 2020 M1 Apache-2.0 OR MIT Yes Details →
7.0.2 01 Feb 2020 M1 Apache-2.0 OR MIT Yes Details →
7.0.1 31 Jan 2020 M1 Apache-2.0 OR MIT Yes Details →
7.0.0 31 Jan 2020 M1 Apache-2.0 OR MIT Yes Details →
6.5.2 27 Jan 2020 M1 Apache-2.0 OR MIT Yes Details →
6.5.1 25 Jan 2020 M1 Apache-2.0 OR MIT Yes Details →
6.5.0 25 Jan 2020 M1 Apache-2.0 OR MIT Yes Details →
6.4.3 21 Jan 2020 M1 Apache-2.0 OR MIT Yes Details →
6.4.2 21 Jan 2020 M1 Apache-2.0 OR MIT Yes Details →
6.4.1 18 Jan 2020 M1 Apache-2.0 OR MIT Yes Details →
6.4.0 14 Jan 2020 M1 Apache-2.0 OR MIT Yes Details →
6.3.5 30 Dec 2019 M1 Apache-2.0 OR MIT Yes Details →
6.3.4 28 Dec 2019 M1 Apache-2.0 OR MIT Yes Details →
6.3.3 21 Dec 2019 M1 Apache-2.0 OR MIT Yes Details →
6.3.2 18 Dec 2019 M1 Apache-2.0 OR MIT Yes Details →
6.3.1 15 Dec 2019 M1 Apache-2.0 OR MIT Yes Details →
6.3.0 14 Dec 2019 M1 Apache-2.0 OR MIT Yes Details →
6.2.10 08 Dec 2019 M1 Apache-2.0 OR MIT Yes Details →
6.2.9 06 Dec 2019 M1 Apache-2.0 OR MIT Yes Details →
6.2.8 06 Dec 2019 M1 Apache-2.0 OR MIT Yes Details →
6.2.7 23 Nov 2019 M1 Apache-2.0 OR MIT Yes Details →
6.2.6 23 Nov 2019 M1 Apache-2.0 OR MIT Yes Details →
6.2.5 23 Nov 2019 M1 Apache-2.0 OR MIT Yes Details →
6.2.4 18 Nov 2019 M1 Apache-2.0 OR MIT Yes Details →
6.2.3 16 Nov 2019 M1 Apache-2.0 OR MIT Yes Details →
6.2.2 16 Nov 2019 M1 Apache-2.0 OR MIT Yes Details →
6.2.1 16 Nov 2019 M1 Apache-2.0 OR MIT Yes Details →
6.2.0 09 Nov 2019 M1 Apache-2.0 OR MIT Yes Details →
6.1.1 08 Nov 2019 M1 Apache-2.0 OR MIT Yes Details →
6.1.0 28 Oct 2019 M1 Apache-2.0 OR MIT Yes Details →
6.0.4 26 Oct 2019 M1 Apache-2.0 OR MIT Yes Details →
6.0.3 21 Oct 2019 M1 Apache-2.0 OR MIT Yes Details →
6.0.2 19 Oct 2019 M1 Apache-2.0 OR MIT Yes Details →
6.0.1 19 Oct 2019 M1 Apache-2.0 OR MIT Yes Details →
6.0.0 18 Oct 2019 M1 Apache-2.0 OR MIT Yes Details →
5.1.0 02 Aug 2019 M1 Apache-2.0 OR MIT Yes Details →
5.0.0 19 Jul 2019 M1 Apache-2.0 OR MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for vis-timeline

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-28487: Cross-site Scripting in vis-timeline 6.8 medium 7.4.4 13 Apr 2021

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 vis-timeline

Is vis-timeline safe to use?

Vulert records 1 vulnerabilities for vis-timeline in npm: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is vis-timeline's Vulert package health score?

Vulert scores vis-timeline 81/100, which reads as in good shape. 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 vis-timeline affected?

No. 8.5.4, 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 vis-timeline should I use?

8.5.4 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 vis-timeline have?

1 vulnerability is recorded for vis-timeline in the npm ecosystem: 0 critical, 0 high, 1 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 vis-timeline vulnerabilities disclosed?

0 vulnerabilities were recorded for vis-timeline in the last 12 months, and the oldest entry in this database dates to 13 Apr 2021. 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 vis-timeline 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 vis-timeline for upcoming vulnerabilities?

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