VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@vltpkg/tar: vulnerability history, versions and safety

@vltpkg/tar is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 42 releases, first recorded in Jan 2026. 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
1 in the last 12 months

Most recent disclosure 28 Jan 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @vltpkg/tar vulnerabilities

Vulert verdict on @vltpkg/tar 1.6.0 i

Updated on 23 Oct 2026

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

Package health score 85/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 1.6.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 28 Jan 2026 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Stars 560 i
  • Last release this month i
  • Licence BSD-2-Clause-Patent 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 @vltpkg/tar, 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
1.6.0 23 Oct 2026 none BSD-2-Clause-Patent — Details →
1.5.0 20 Oct 2026 none BSD-2-Clause-Patent — Details →
1.4.0 14 Oct 2026 none BSD-2-Clause-Patent — Details →
1.3.8 09 Oct 2026 none BSD-2-Clause-Patent — Details →
1.3.7 06 Oct 2026 none BSD-2-Clause-Patent — Details →
1.3.6 03 Oct 2026 none BSD-2-Clause-Patent — Details →
1.3.5 02 Oct 2026 none BSD-2-Clause-Patent — Details →
1.3.4 01 Oct 2026 none BSD-2-Clause-Patent — Details →
1.3.3 01 Oct 2026 none BSD-2-Clause-Patent — Details →
1.3.2 30 Sep 2026 none BSD-2-Clause-Patent — Details →
1.3.1 29 Sep 2026 none BSD-2-Clause-Patent — Details →
1.3.0 28 Sep 2026 none BSD-2-Clause-Patent — Details →
1.2.0 25 Sep 2026 none BSD-2-Clause-Patent — Details →
1.1.1 20 Sep 2026 none BSD-2-Clause-Patent — Details →
1.1.0 18 Sep 2026 none BSD-2-Clause-Patent — Details →
1.0.10 10 Sep 2026 none BSD-2-Clause-Patent — Details →
1.0.9 09 Sep 2026 none BSD-2-Clause-Patent — Details →
1.0.8 08 Sep 2026 none BSD-2-Clause-Patent — Details →
1.0.7 28 Aug 2026 none BSD-2-Clause-Patent — Details →
1.0.6 27 Aug 2026 none BSD-2-Clause-Patent — Details →
1.0.5 25 Aug 2026 none BSD-2-Clause-Patent — Details →
1.0.4 19 Aug 2026 none BSD-2-Clause-Patent — Details →
1.0.3 17 Aug 2026 none BSD-2-Clause-Patent — Details →
1.0.2 07 Aug 2026 none BSD-2-Clause-Patent — Details →
1.0.1 04 Aug 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.34 04 Aug 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.33 03 Aug 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.32 03 Jun 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.31 22 May 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.30 21 May 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.29 13 May 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.27 24 Apr 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.26 23 Apr 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.25 17 Apr 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.24 01 Apr 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.23 19 Mar 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.22 19 Mar 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.18 04 Feb 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.17 03 Feb 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.16 29 Jan 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.15 26 Jan 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.14 13 Jan 2026 none BSD-2-Clause-Patent — Details →
1.0.0-rc.13 19 Dec 2025 none BSD-2-Clause-Patent — Details →
1.0.0-rc.12 17 Dec 2025 none BSD-2-Clause-Patent — Details →
1.0.0-rc.11 13 Dec 2025 none BSD-2-Clause-Patent — Details →
1.0.0-rc.10 10 Dec 2025 none BSD-2-Clause-Patent — Details →
1.0.0-rc.9 08 Dec 2025 M1 BSD-2-Clause-Patent Yes Details →
1.0.0-rc.8 04 Dec 2025 M1 BSD-2-Clause-Patent Yes Details →
1.0.0-rc.7 28 Nov 2025 M1 BSD-2-Clause-Patent Yes Details →
1.0.0-rc.6 26 Nov 2025 M1 BSD-2-Clause-Patent Yes Details →
1.0.0-rc.5 21 Nov 2025 M1 BSD-2-Clause-Patent Yes Details →
1.0.0-rc.4 19 Nov 2025 M1 BSD-2-Clause-Patent Yes Details →
1.0.0-rc.3 14 Nov 2025 M1 BSD-2-Clause-Patent Yes Details →
1.0.0-rc.2 22 Oct 2025 M1 BSD-2-Clause-Patent Yes Details →
1.0.0-rc.1 14 Oct 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-32 07 Oct 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-31 06 Oct 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-30 18 Sep 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-29 04 Sep 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-28 04 Sep 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-27 04 Sep 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-26 03 Sep 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-25 02 Sep 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-24 30 Aug 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-23 23 Aug 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-22 20 Aug 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-21 16 Aug 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-20 12 Aug 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-19 06 Aug 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-18 21 Jul 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-17 09 Jul 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-16 25 Jun 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-15 16 Jun 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-14 03 Jun 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-13 20 May 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-12 03 May 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-11 01 May 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-10 25 Apr 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-9 16 Apr 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-8 28 Mar 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-7 21 Mar 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-6 19 Mar 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-5 18 Mar 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-4 17 Mar 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-3 07 Mar 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-2 07 Mar 2025 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-0.1730724342581 04 Nov 2024 M1 BSD-2-Clause-Patent Yes Details →
0.0.0-0.1730239248325 29 Oct 2024 M1 BSD-2-Clause-Patent Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for @vltpkg/tar

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Path Traversal Vulnerability in @vltpkg/tar Package 5.9 medium 1.0.0-rc.10 28 Jan 2026

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 @vltpkg/tar

Is @vltpkg/tar safe to use?

Vulert records 1 vulnerabilities for @vltpkg/tar 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 @vltpkg/tar's Vulert package health score?

Vulert scores @vltpkg/tar 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 @vltpkg/tar affected?

No. 1.6.0, 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.

How many vulnerabilities does @vltpkg/tar have?

1 vulnerability is recorded for @vltpkg/tar 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 @vltpkg/tar vulnerabilities disclosed?

1 vulnerability was recorded for @vltpkg/tar in the last 12 months, and the oldest entry in this database dates to 28 Jan 2026. 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 @vltpkg/tar 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 @vltpkg/tar for upcoming vulnerabilities?

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