Creating Electron app packages
88%
Total Score
healthy
Healthy: active Electron-backed maintenance and verified publishing outweigh a limited workflow hygiene concern.
The repository has no published security policy, leaving vulnerability reporting and response expectations less transparent than they could be.
All 5 workflows were analyzed successfully; actions are pinned and permissions are read-only, but the audit found two high-confidence template-injection findings in docs.yml. The findings do not include an untrusted checkout or script-injection sink, so this is a hygiene concern rather than a severe dependency-health risk.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-222906 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. @electron/asar is vulnerable to Path Traversal in versions 3.2.1 - 4.2.0. | 3.2.1 - 4.2.0 | Medium |
AIKIDO-2024-10255 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. @electron/asar is vulnerable to UNIX Symbolic Link (Symlink) Following in versions 0.2.0 - 3.2.10. | 0.2.0 - 3.2.10 | Medium |
| Dependency | Last Release | Score |
|---|---|---|
glob Version ^13.0.2 | — | — |
minimatch Version ^10.0.1 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.