Home / npm packages / env-paths
Every file of env-paths@4.0.0 as published on npm: 5 files, 9.6 KB. Search them by exact text or regex, in milliseconds.
It uses: none of the APIs we check for.
| API | In env-paths | |
|---|---|---|
| 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 | No | Who does |
| 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 |
|---|---|
index.d.ts | 2.8 KB |
readme.md | 2.7 KB |
index.js | 2.0 KB |
license | 1.1 KB |
package.json | 930 B |
Version 4.0.0 of env-paths publishes 5 files of source, 9.6 KB in all, not counting images, fonts and source maps.
No: env-paths doesn't call eval() anywhere in its published files.
No: env-paths doesn't use child_process anywhere in its published files.
No: env-paths 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.