VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

node-tar: vulnerability history, versions and safety

node-tar is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 1 release, first recorded in Mar 2024. 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 node-tar vulnerabilities

Vulert verdict on node-tar 1.0.0 i

Updated on 23 Oct 2026

Action needed: 1.0.0 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 45/100
  • Security No known security issues
  • Maintenance Deprecated
  • Popularity Niche
  • Community Not enough data

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

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 1.0.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 22 Mar 2024 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 10 packages i
  • Last release 47 months ago i
  • Licence ISC 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 node-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.0.0 08 Nov 2022 M1 ISC Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 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 node-tar

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-28863: Denial of Service Vulnerability in node-tar 6.5 medium 6.2.1 22 Mar 2024

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 node-tar

Is node-tar safe to use?

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

Vulert scores node-tar 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 node-tar affected?

Yes. 1.0.0, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of node-tar should I use?

1.0.0 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 node-tar have?

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

0 vulnerabilities were recorded for node-tar in the last 12 months, and the oldest entry in this database dates to 22 Mar 2024. 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 node-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 node-tar for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the node-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.