electron-to-chromium
npmIs electron-to-chromium safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for electron-to-chromium v1.5.286. Trust score: 65/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.
Install (safety-checked)
electron-to-chromium Passed Security Checks
No security concerns detected
0
0
0
No Concerns Detected
No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.
This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.
electron-to-chromium Capabilities & Permissions
No system capabilities detected for electron-to-chromium. It does not appear to access the network, filesystem, spawn processes, or use native modules. No capability concerns identified for use with AI coding agents.
AGENTS.md for electron-to-chromium
Good instructions lead to good results. brin adds electron-to-chromium documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
electron-to-chromium Documentation & Source Code
For the full electron-to-chromium README, API documentation, and source code, visit the official package registry.