Home / npm packages / tar-stream
Every file of tar-stream@3.2.2 as published on npm: 9 files, 34 KB. Search them by exact text or regex, in milliseconds.
It uses: the fs module.
| API | In tar-stream | |
|---|---|---|
| eval() runs a string as JavaScript | No | Who does |
| new Function() builds a function from a string, like eval (with or without new) | No | Who does |
| child_process starts other programs | No | Who does |
| process.env reads environment variables | No | Who does |
| the fs module reads and writes files | Yes: 2 files e.g. constants.js | See the lines |
| http / https makes or serves HTTP requests with Node's own modules | No | Who does |
| fetch() makes HTTP requests | No | Who does |
| XMLHttpRequest makes HTTP requests the old browser way | No | Who does |
| crypto hashes, encrypts or makes random numbers | No | Who does |
| WebAssembly loads WebAssembly code | No | Who does |
| document.cookie reads or writes browser cookies | No | Who does |
| install scripts runs a script when it's installed | No | Who does |
Exact matches in the published files, so a mention in a comment counts too: open the lines to check.
| File | Size |
|---|---|
extract.js | 9.6 KB |
headers.js | 8.6 KB |
pack.js | 6.3 KB |
README.md | 5.6 KB |
index.d.ts | 1.3 KB |
package.json | 1.2 KB |
LICENSE | 1.1 KB |
constants.js | 258 B |
index.js | 72 B |
Version 3.2.2 of tar-stream publishes 9 files of source, 34 KB in all, not counting images, fonts and source maps.
No: tar-stream doesn't call eval() anywhere in its published files.
No: tar-stream doesn't use child_process anywhere in its published files.
No: tar-stream has no preinstall, install or postinstall script in its package.json.
The same engine answers over your documents and repositories: exact text and regex, every match counted, from your code or your AI agent.