VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

vis: vulnerability history, versions and safety

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

Vulert verdict on vis 4.21.0-EOL i

Updated on 23 Oct 2026

Good news: 4.21.0-EOL, the version you would install today, has no known vulnerabilities.

Package health score 45/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Widely used
  • Community Quiet

The registry marks the latest release as deprecated, which caps this score.

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

  • Current release 4.21.0-EOL — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 31 packages i
  • Stars 7,802 i
  • OpenSSF scorecard 1/10 i
  • Last release 86 months ago i
  • Licence Apache-2.0 OR MIT 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 vis, 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
4.21.0-EOL 28 Jul 2019 none Apache-2.0 OR MIT — Details →
4.21.0 12 Oct 2017 none Apache-2.0 OR MIT — Details →
4.20.1-SNAPSHOT 12 Oct 2017 none Apache-2.0 OR MIT — Details →
4.20.1 02 Jul 2017 none Apache-2.0 OR MIT — Details →
4.20.0 21 May 2017 none Apache-2.0 OR MIT — Details →
4.19.1 19 Mar 2017 none Apache-2.0 OR MIT — Details →
4.19.0 18 Mar 2017 none Apache-2.0 OR MIT — Details →
4.18.1 29 Jan 2017 none Apache-2.0 OR MIT — Details →
4.18.0 15 Jan 2017 none Apache-2.0 OR MIT — Details →
4.17.0 05 Nov 2016 none Apache-2.0 OR MIT — Details →
4.16.1 18 Apr 2016 none Apache-2.0 OR MIT — Details →
4.16.0 07 Apr 2016 none Apache-2.0 OR MIT — Details →
4.15.1 08 Mar 2016 none Apache-2.0 OR MIT — Details →
4.15.0 23 Feb 2016 none Apache-2.0 OR MIT — Details →
4.14.0 04 Feb 2016 none Apache-2.0 OR MIT — Details →
4.13.0 01 Feb 2016 none Apache-2.0 OR MIT — Details →
4.12.0 08 Jan 2016 none Apache-2.0 OR MIT — Details →
4.11.0 18 Dec 2015 none Apache-2.0 OR MIT — Details →
4.10.0 27 Nov 2015 none Apache-2.0 OR MIT — Details →
4.9.0 01 Oct 2015 none Apache-2.0 OR MIT — Details →
4.8.2 14 Sep 2015 none Apache-2.0 OR MIT — Details →
4.8.1 07 Sep 2015 none Apache-2.0 OR MIT — Details →
4.8.0 28 Aug 2015 none Apache-2.0 OR MIT — Details →
4.7.0 27 Jul 2015 none Apache-2.0 OR MIT — Details →
4.6.0 22 Jul 2015 none Apache-2.0 OR MIT — Details →
4.5.1 20 Jul 2015 none Apache-2.0 OR MIT — Details →
4.5.0 17 Jul 2015 none Apache-2.0 OR MIT — Details →
4.4.0 03 Jul 2015 none Apache-2.0 OR MIT — Details →
4.3.0 16 Jun 2015 none Apache-2.0 OR MIT — Details →
4.2.0 05 Jun 2015 none Apache-2.0 OR MIT — Details →
4.1.0 28 May 2015 none Apache-2.0 OR MIT — Details →
4.0.0 22 May 2015 none Apache-2.0 OR MIT — Details →
3.12.0 07 Apr 2015 none Apache-2.0 OR MIT — Details →
3.11.0 05 Mar 2015 none Apache-2.0 OR MIT — Details →
3.10.0 11 Feb 2015 none Apache-2.0 OR MIT — Details →
3.9.1 22 Jan 2015 none Apache-2.0 OR MIT — Details →
3.9.0 16 Jan 2015 none Apache-2.0 OR MIT — Details →
3.8.0 09 Jan 2015 none Apache-2.0 OR MIT — Details →
3.7.2 09 Dec 2014 none Apache-2.0 OR MIT — Details →
3.7.1 28 Nov 2014 none Apache-2.0 OR MIT — Details →
3.7.0 14 Nov 2014 none Apache-2.0 OR MIT — Details →
3.6.4 07 Nov 2014 none Apache-2.0 OR MIT — Details →
3.6.3 28 Oct 2014 none Apache-2.0 OR MIT — Details →
3.6.2 24 Oct 2014 none Apache-2.0 OR MIT — Details →
3.6.1 22 Oct 2014 none Apache-2.0 OR MIT — Details →
3.6.0 21 Oct 2014 none Apache-2.0 OR MIT — Details →
3.5.0 16 Sep 2014 none Apache-2.0 OR MIT — Details →
3.4.2 12 Sep 2014 none Apache-2.0 OR MIT — Details →
3.4.1 11 Sep 2014 none Apache-2.0 OR MIT — Details →
3.4.0 10 Sep 2014 none Apache-2.0 OR MIT — Details →
3.3.0 29 Aug 2014 none Apache-2.0 OR MIT — Details →
3.2.0 14 Aug 2014 none Apache-2.0 OR MIT — Details →
3.1.0 22 Jul 2014 none Apache-2.0 OR MIT — Details →
3.0.0 07 Jul 2014 none Apache-2.0 OR MIT — Details →
2.0.0 19 Jun 2014 none Apache-2.0 OR MIT — Details →
1.1.0 06 Jun 2014 none Apache-2.0 OR MIT — Details →
1.0.2 28 May 2014 none Apache-2.0 OR MIT — Details →
1.0.1 09 May 2014 none Apache-2.0 OR MIT — Details →
1.0.0 02 May 2014 none Apache-2.0 OR MIT — Details →
0.7.4 18 Apr 2014 none Apache-2.0 OR MIT — Details →
0.7.3 16 Apr 2014 none Apache-2.0 OR MIT — Details →
0.7.2 09 Apr 2014 none Apache-2.0 OR MIT — Details →
0.7.1 27 Mar 2014 none Apache-2.0 OR MIT — Details →
0.7.0 07 Mar 2014 none Apache-2.0 OR MIT — Details →
0.6.1 06 Mar 2014 none Apache-2.0 OR MIT — Details →
0.6.0 05 Mar 2014 none Apache-2.0 OR MIT — Details →
0.5.1 20 Feb 2014 none Apache-2.0 OR MIT — Details →
0.5.0 20 Feb 2014 none Apache-2.0 OR MIT — Details →
0.4.0 31 Jan 2014 none Apache-2.0 OR MIT — Details →
0.3.0 14 Jan 2014 none Apache-2.0 OR MIT — Details →
0.2.0 20 Sep 2013 none Apache-2.0 OR MIT — Details →
0.1.0 20 Jun 2013 none Apache-2.0 OR MIT — Details →
0.0.9 07 Jun 2013 none Apache-2.0 OR MIT — Details →
0.0.8 03 May 2013 none Apache-2.0 OR MIT — Details →
0.0.7 25 Apr 2013 none Apache-2.0 OR MIT — Details →
0.0.6 25 Apr 2013 none Apache-2.0 OR MIT — Details →

All 76 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 vis

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 vis

Is vis safe to use?

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

Vulert scores vis 45/100, which reads as risky. 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). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of vis affected?

No. 4.21.0-EOL, 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 should I use?

4.21.0-EOL 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 have?

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

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

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