tar 0.1.7

tar for node

tar@0.1.7 was published on 2011-12-01. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is ~0.5.9 || 0.6 || 0.7 || 0.8.

Deprecated: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me

All tar versions · Permanent reference to 0.1.7 · Latest release

Package specifications

Version0.1.7
License declarationNot declared
Published2011-12-01T03:12:57.060Z
Node.js requirement~0.5.9 || 0.6 || 0.7 || 0.8
Type declarationsNot declared
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrytar.js
Side effects declarationNot declared
Direct advisories17
Resolved graph dependencies21
Repository stars923
Repository forks286

Install tar 0.1.7

npm install tar@0.1.7
pnpm add tar@0.1.7
yarn add tar@0.1.7

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

Known direct advisories

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review0/10 — Found 1/30 approved changesets -- score normalized to 0
Maintained10/10 — 16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness