npm/node-tar · audit

npm/node-tar ↗ · 188badd · Aug 21, 2026, 11:38 PM

No deterministic issues foundNo problems found by this automatic checkNo issues found

Free scan · deterministic evidence onlyFree scan · found by automatic checks onlyFree scan · deterministic evidence only

The secret and dependency scanners surfaced nothing verdict-bearing in what they scanned. This is not a clean bill of health. These two scanners cover a sliver of production-readiness — the 14 dimensions that actually decide whether you ship are unaudited below. Run Audit for the verdict.

The checks for leaked passwords and known package bugs found nothing to flag. This does not mean your code is safe. These two checks cover only a small slice of what matters — the 14 areas that actually decide whether your code is ready to ship are not checked yet. Run Audit for the full verdict.

No deterministic issues found — not a clean bill of health. 14 dimensions remain unaudited. Run Audit for the verdict.

202 of 237 files scanned (85%). Nothing was cut short by a limit — the rest is mostly images, generated output, and other non-source content this audit doesn't read.

What this meansWhat this means for youWhat this means

Two scanners read 202 of 237 files: one for committed credentials, one for known vulnerabilities in your dependencies. Neither found anything. That is not a clean bill of health. These two checks cover a narrow slice of what decides whether software is ready to ship. All 14 dimensions — architecture, privacy, reliability, AI-generated-code risk and the rest — are unexamined here. Deep AI is the tier that issues a verdict. This scan does not.

Read it:

Worth knowing, not blocking

35 found · 23 packages · 35 devDependencies

Test/example/doc credentials and devDependency or moderate/low CVEs. Surfaced as context — these never force the worst verdict.Passwords found in test, example or documentation files, and lower-severity security bugs in packages only used while building the project. Shown for context — these never cause the worst possible result.Context only — test/example secrets, dev-only or moderate/low CVEs. Never verdict-forcing.

dev depnpm brace-expansion3 in 1 version

1.1.11 — GHSA-3jxr-9vmj-r5cp, GHSA-f886-m6hf-6m8v, GHSA-mh99-v99m-4gvg

brace-expansion: DoS via exponential-time expansion of consecutive non-expanding {} groups — devDependency

brace-expansion: Zero-step sequence causes process hang and memory exhaustion — devDependency

brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash — devDependency

dev depnpm js-yaml3 in 1 version

3.14.1 — GHSA-52cp-r559-cp3m, GHSA-5p4m-2wfm-xmqj, GHSA-h67p-54hq-rp68

js-yaml: YAML merge-key chains can force quadratic CPU consumption — devDependency

JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported — devDependency

JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases — devDependency

dev depnpm minimatch3 in 1 version

3.0.4 — GHSA-23c5-xmqv-rm74, GHSA-3ppc-4f35-3m26, GHSA-7r86-cg39-jmmj

minimatch ReDoS: nested *() extglobs generate catastrophically backtracking regular expressions — devDependency

minimatch has a ReDoS via repeated wildcards with non-matching literal in pattern — devDependency

minimatch has ReDoS: matchOne() combinatorial backtracking via multiple non-adjacent GLOBSTAR segments — devDependency

dev depnpm tar-fs3 in 1 version

1.16.3 — GHSA-8cj5-5rvv-wf4v, GHSA-pq67-2wwv-3xjx, GHSA-vj76-c3g6-qr5v

tar-fs can extract outside the specified dir with a specific tarball — devDependency

tar-fs Vulnerable to Link Following and Path Traversal via Extracting a Crafted tar File — devDependency

tar-fs has a symlink validation bypass if destination directory is predictable with a specific tarball — devDependency

dev depnpm flatted2 in 1 version

3.2.2 — GHSA-25h7-pfq9-p65f, GHSA-rf6f-7fwh-wjgh

flatted vulnerable to unbounded recursion DoS in parse() revive phase — devDependency

Prototype Pollution via parse() in NodeJS flatted — devDependency

dev depnpm form-data2 in 1 version

2.3.3 — GHSA-fjxv-7rqg-78g4, GHSA-hmw2-7cc7-3qxx

form-data uses unsafe random function in form-data for choosing boundary — devDependency

form-data: CRLF injection in form-data via unescaped multipart field names and filenames — devDependency

dev depnpm picomatch2 in 1 version

2.3.0 — GHSA-3v7f-55p6-f55p, GHSA-c2c7-rcm5-vvqj

Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching — devDependency

Picomatch has a ReDoS vulnerability via extglob quantifiers — devDependency

dev depnpm qs2 in 1 version

6.5.2 — GHSA-6rw7-vpxm-498p, GHSA-hrpp-h998-j3pp

qs's arrayLimit bypass in its bracket notation allows DoS via memory exhaustion — devDependency

qs vulnerable to Prototype Pollution — devDependency

dev depnpm @babel/core@7.15.0GHSA-4x5r-pxfx-6jf8

@babel/core: Arbitrary File Read via sourceMappingURL Comment — devDependency

dev depnpm @babel/helpers@7.14.8GHSA-968p-4wvh-cqc8

Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups — devDependency

dev depnpm @babel/traverse@7.15.0GHSA-67hx-6x53-jw92

Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code — devDependency

dev depnpm ajv@6.12.6GHSA-2g4f-4pwh-qvx6

ajv has ReDoS when using `$data` option — devDependency

dev depnpm ansi-regex@5.0.0GHSA-93q8-gq69-wqmw

Inefficient Regular Expression Complexity in chalk/ansi-regex — devDependency

dev depnpm braces@3.0.2GHSA-grv7-fg5c-xmjg

Uncontrolled resource consumption in braces — devDependency

dev depnpm cross-spawn@7.0.3GHSA-3xgq-45jj-v275

Regular Expression Denial of Service (ReDoS) in cross-spawn — devDependency

dev depnpm diff@4.0.2GHSA-73rr-hh4g-fpgx

jsdiff has a Denial of Service vulnerability in parsePatch and applyPatch — devDependency

dev depnpm json-schema@0.2.3GHSA-896r-f27r-55mw

json-schema is vulnerable to Prototype Pollution — devDependency

dev depnpm json5@2.2.0GHSA-9c47-m6qq-7p4h

Prototype Pollution in JSON5 via Parse Method — devDependency

dev depnpm minimist@1.2.5GHSA-xvch-5gv4-984h

Prototype Pollution in minimist — devDependency

dev depnpm request@2.88.2GHSA-p8p7-x288-28g6

Server-Side Request Forgery in Request — devDependency

dev depnpm semver@7.3.5GHSA-c2qf-rxjj-qqgw

semver vulnerable to Regular Expression Denial of Service — devDependency

dev depnpm tough-cookie@2.5.0GHSA-72xf-g2v4-qvf3

tough-cookie Prototype Pollution vulnerability — devDependency

dev depnpm uuid@3.4.0GHSA-w5hq-g745-h8pq

uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided — devDependency

AI audit for npm/node-tar · all 14 dimensions · usually within 15 minutes*AI check for npm/node-tar · all 14 areas · usually within 15 minutes*AI audit · npm/node-tar · 14 dimensions · usually within 15 minutes*

Audit — your first Audit is free. After that, about $5.Needs a free GitHub or Google sign-inNeeds a free sign-in with GitHub or GoogleNeeds a free GitHub or Google sign-inThe free scan stays unlimitedYou can run the free scan as many times as you likeThe free scan stays unlimited

14 things we haven't looked at yet14 things we haven't checked yet14 things unaudited

Security logic, privacy, reliability, AI-generated-code risk and 10 more — unaudited, not clean.Security logic, privacy, reliability, AI-generated-code risk and 10 more — not checked yet, which is different from safe.Security, privacy, reliability, AI-generated-code risk, 10 more: unaudited, not clean.

The free scan reasons across none of these. Absence of findings is reported as unaudited, not safe. Opus 4.8 reads the code semantically and scores every one — with evidence, business impact, and a fix per finding.

The free scan doesn't look at any of these. If nothing is flagged here, that means it wasn't checked — not that it's safe. Opus 4.8 (the AI model behind the audit) reads and understands your code and scores every one of these — with evidence, the real-world impact, and a fix for each finding.

The free scan doesn't reason across these — unaudited, not safe. Opus 4.8 scores each, with evidence, impact, and a fix.

SecurityPriority: Core

Privacy & CompliancePriority: Core

Reliability & ResiliencePriority: Core

Code Quality & ArchitecturePriority: Important

AI / Vibe Coding RiskPriority: Important

Performance & ScalabilityPriority: Important

Infrastructure & DevOpsPriority: Important

Data LayerPriority: Important

Business & Product RiskPriority: Supporting

Developer ExperiencePriority: Supporting

Accessibility & UXPriority: Supporting

ObservabilityPriority: Supporting

Maintainability ForecastPriority: Specialized

IP & Novelty ExposurePriority: Specialized

Modules run (2)

Hardcoded Secret ScanDependency Vulnerability Scan

Hover a module for why it was selected. See every check nittim can run.

Scanned 202 of 237 files · npm/node-tar
Dependency manifests: 1 package root found, 1 scanned — package list truncated at the vulnerability-lookup limit.

README badgeBadge for your project's readme fileREADME badge

[![nittim](https://nittim.com/api/badge/npm/node-tar)](https://nittim.com)