Home / npm packages / electron-to-chromium

electron-to-chromium source code

Every file of electron-to-chromium@1.5.444 as published on npm: 12 files, 203 KB. Search them by exact text or regex, in milliseconds.

It uses: none of the APIs we check for.

What electron-to-chromium uses

API	In electron-to-chromium
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.

How many files are in electron-to-chromium?

Version 1.5.444 of electron-to-chromium publishes 12 files of source, 203 KB in all, not counting images, fonts and source maps.

Does electron-to-chromium use eval?

No: electron-to-chromium doesn't call eval() anywhere in its published files.

Does electron-to-chromium start other programs?

No: electron-to-chromium doesn't use child_process anywhere in its published files.

Does electron-to-chromium run an install script?

No: electron-to-chromium 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.