Home / npm packages / string_decoder
Every file of string_decoder@1.3.0 as published on npm: 4 files, 14 KB. Search them by exact text or regex, in milliseconds.
It uses: none of the APIs we check for.
| API | In string_decoder | |
|---|---|---|
| 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 |
|---|---|
lib/string_decoder.js | 9.5 KB |
LICENSE | 2.3 KB |
README.md | 1.8 KB |
package.json | 823 B |
Version 1.3.0 of string_decoder publishes 4 files of source, 14 KB in all, not counting images, fonts and source maps.
No: string_decoder doesn't call eval() anywhere in its published files.
No: string_decoder doesn't use child_process anywhere in its published files.
No: string_decoder 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.