Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Generated on May 29, 2024 via pnpm

tar-fs 1.16.1

filesystem bindings for tar-stream
Package summary
Share
2
issues
2
high severity
vulnerability
2
2
licenses
21
MIT
4
ISC
Package created
21 Dec 2013
Version published
29 Apr 2018
Maintainers
2
Total deps
25
Direct deps
4
License
MIT

Issues

2

2 high severity issues

high
Recommendation: Upgrade to version 1.16.2 or later
via: tar-fs@1.16.1
Recommendation: Upgrade to version 1.16.2 or later
via: tar-fs@1.16.1
Collapse
Expand

Licenses

MIT License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
Cannot
hold-liable
Must
include-copyright
include-license
21 Packages, Including:
bl@1.2.3
buffer-alloc-unsafe@1.1.0
buffer-alloc@1.2.0
buffer-fill@1.0.0
core-util-is@1.0.3
end-of-stream@1.4.4
fs-constants@1.0.0
isarray@1.0.0
minimist@1.2.8
mkdirp@0.5.6
process-nextick-args@2.0.1
pump@1.0.3
readable-stream@2.3.8
safe-buffer@5.1.2
safe-buffer@5.2.1
string_decoder@1.1.1
tar-fs@1.16.1
tar-stream@1.6.2
to-buffer@1.1.1
util-deprecate@1.0.2
xtend@4.0.2

ISC License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
Cannot
hold-liable
Must
include-copyright
include-license
4 Packages, Including:
chownr@1.1.4
inherits@2.0.4
once@1.4.0
wrappy@1.0.2
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

4
All Dependencies CSV
β“˜ This is a list of tar-fs 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities
chownr1.1.42.17 kBISC
prod
mkdirp0.5.62.95 kBMIT
prod
pump1.0.32.92 kBMIT
prod
tar-stream1.6.28.13 kBMIT
prod

Visualizations

Frequently Asked Questions

What does tar-fs do?

Tar-fs is an npm package that provides filesystem bindings for tar-stream. It is designed to pack directories into tarballs and extract tarballs into directories. It is ideal for handling tarball files in JavaScript applications, but note that it does not support gunzip on its own. To work with .tar.gz files, it is recommended to use another utility, such as gunzip-maybe, in conjunction with tar-fs.

How do you use tar-fs?

Using tar-fs is relatively straightforward. After installing the package via npm with npm install tar-fs, you can incorporate it into your project with the required statement like const tar = require('tar-fs').

Here is an example of how to use tar-fs to pack a directory into a tarball:

const tar = require('tar-fs')
const fs = require('fs')

// packing a directory
tar.pack('./my-directory').pipe(fs.createWriteStream('my-tarball.tar'))

And to extract a tarball into a directory, use the following:

// extracting a directory
fs.createReadStream('my-other-tarball.tar').pipe(tar.extract('./my-other-directory'))

It also provides additional options like filtering specific files when packing or extracting, defining entries to pack, modifying the headers, altering input/output file streams, setting file/directory modes, and more.

Where are the tar-fs docs?

Documentation and examples for tar-fs can be found in the README file in its GitHub repository at https://github.com/mafintosh/tar-fs.git. This README includes details about the package's functions and options, as well as code examples. For an intensive understanding of the tar-fs package and its full capabilities, it is a great resource.