Home / npm packages / call-bind-apply-helpers
Every file of call-bind-apply-helpers@1.0.2 as published on npm: 21 files, 16 KB. Search them by exact text or regex, in milliseconds.
It uses: none of the APIs we check for.
| API | In call-bind-apply-helpers | |
|---|---|---|
| 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 |
|---|---|
test/index.js | 2.7 KB |
package.json | 2.5 KB |
README.md | 2.3 KB |
index.d.ts | 2.2 KB |
CHANGELOG.md | 1.9 KB |
LICENSE | 1.1 KB |
applyBind.d.ts | 614 B |
.github/FUNDING.yml | 594 B |
index.js | 511 B |
actualApply.js | 280 B |
applyBind.js | 264 B |
.eslintrc | 232 B |
.nycrc | 139 B |
reflectApply.js | 132 B |
tsconfig.json | 115 B |
functionApply.js | 99 B |
functionCall.js | 97 B |
reflectApply.d.ts | 82 B |
functionApply.d.ts | 34 B |
functionCall.d.ts | 33 B |
actualApply.d.ts | 23 B |
Version 1.0.2 of call-bind-apply-helpers publishes 21 files of source, 16 KB in all, not counting images, fonts and source maps.
No: call-bind-apply-helpers doesn't call eval() anywhere in its published files.
No: call-bind-apply-helpers doesn't use child_process anywhere in its published files.
No: call-bind-apply-helpers 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.