gitsafehub
github.com/jazzyarchitects/electron-music-player ↗

jazzyarchitects/electron-music-player

scanned 2026-08-15 · git 8f81d94
4 of 6 checks flagged a security issue
🔴 Needs attention
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets5Vulnerable dependencies17Known OSS vulnerabilities100Risky code patternsMalicious dependencies1Project health

Security checks

Leaked secrets — Gitleaks 5 found

API keys, passwords or tokens committed into the repo.

  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    modules/globalShortcuts.js:16
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    modules/globalShortcuts.js:34
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    globalShortcuts.js:18
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    globalShortcuts.js:30
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    globalShortcuts.js:38
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivy 17 found · 2 serious

Packages you depend on that have known security holes (CVEs).

  • Serious CVE-2019-10744 nodejs-lodash: prototype pollution in defaultsDeep function leading to modifying properties
    yarn.lock
    A package you depend on has a known security hole (CVE-2019-10744). Fix: Update that package to its patched version.
  • Serious CVE-2021-23358 nodejs-underscore: Arbitrary code execution via the template function
    yarn.lock
    A package you depend on has a known security hole (CVE-2021-23358). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-43138 async: Prototype Pollution in async
    yarn.lock
    A package you depend on has a known security hole (CVE-2021-43138). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-7788 nodejs-ini: Prototype pollution via malicious INI file
    yarn.lock
    A package you depend on has a known security hole (CVE-2020-7788). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-16487 lodash: Prototype pollution in utilities function
    yarn.lock
    A package you depend on has a known security hole (CVE-2018-16487). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-8203 nodejs-lodash: prototype pollution in zipObjectDeep function
    yarn.lock
    A package you depend on has a known security hole (CVE-2020-8203). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-23337 nodejs-lodash: command injection via template
    yarn.lock
    A package you depend on has a known security hole (CVE-2021-23337). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-4800 lodash: lodash: Arbitrary code execution via untrusted input in template imports
    yarn.lock
    A package you depend on has a known security hole (CVE-2026-4800). Fix: Update that package to its patched version.
  • Worth fixing CVE-2019-1010266 lodash: uncontrolled resource consumption in Data handler causing denial of service
    yarn.lock
    A package you depend on has a known security hole (CVE-2019-1010266). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-28500 nodejs-lodash: ReDoS via the toNumber, trim and trimEnd functions
    yarn.lock
    A package you depend on has a known security hole (CVE-2020-28500). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-13465 lodash: prototype pollution in _.unset and _.omit functions
    yarn.lock
    A package you depend on has a known security hole (CVE-2025-13465). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-2950 lodash: Lodash: Prototype pollution allows deletion of built-in prototype properties via array path bypass
    yarn.lock
    A package you depend on has a known security hole (CVE-2026-2950). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-32256 music-metadata has an infinite loop vulnerability in ASF parser
    yarn.lock
    A package you depend on has a known security hole (CVE-2026-32256). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-21803 nconf: Prototype pollution in memory store
    yarn.lock
    A package you depend on has a known security hole (CVE-2022-21803). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-27601 Underscore.js: Underscore.js: Denial of Service via recursive data structures in flatten and isEqual functions
    yarn.lock
    A package you depend on has a known security hole (CVE-2026-27601). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-7774 nodejs-y18n: prototype pollution vulnerability
    yarn.lock
    A package you depend on has a known security hole (CVE-2020-7774). Fix: Update that package to its patched version.
  • Minor CVE-2018-3721 lodash: Prototype pollution in utilities function
    yarn.lock
    A package you depend on has a known security hole (CVE-2018-3721). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 100 found · 9 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious GHSA-hr2v-3952-633q Prototype Pollution in deep-extend
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2018-3750). Fix: Update that package to its patched version.
  • Serious GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2025-7783). Fix: Update that package to its patched version.
  • Serious GHSA-896r-f27r-55mw json-schema is vulnerable to Prototype Pollution
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2021-3918). Fix: Update that package to its patched version.
  • Serious GHSA-jf85-cpcp-j695 Prototype Pollution in lodash
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2019-10744). Fix: Update that package to its patched version.
  • Serious GHSA-jf85-cpcp-j695 Prototype Pollution in lodash
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2019-10744). Fix: Update that package to its patched version.
  • Serious GHSA-xvch-5gv4-984h Prototype Pollution in minimist
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2021-44906). Fix: Update that package to its patched version.
  • Serious GHSA-xvch-5gv4-984h Prototype Pollution in minimist
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2021-44906). Fix: Update that package to its patched version.
  • Serious GHSA-23hp-3jrh-7fpw node-tar: Decompression/parse DoS via unlimited input
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2026-59873). Fix: Update that package to its patched version.
  • Serious GHSA-cf4h-3jhx-xvhq Arbitrary Code Execution in underscore
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2021-23358). Fix: Update that package to its patched version.
  • Worth fixing GHSA-2g4f-4pwh-qvx6 ajv has ReDoS when using `$data` option
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2025-69873). Fix: Update that package to its patched version.
  • Worth fixing GHSA-v88g-cgmw-v5xw Prototype Pollution in Ajv
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2020-15366). Fix: Update that package to its patched version.
  • Worth fixing GHSA-fwr7-v2mv-hh25 Prototype Pollution in async
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2021-43138). Fix: Update that package to its patched version.
  • Worth fixing GHSA-pp7h-53gx-mx7r Remote Memory Exposure in bl
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2020-8244). Fix: Update that package to its patched version.
  • Worth fixing GHSA-3jxr-9vmj-r5cp brace-expansion: DoS via exponential-time expansion of consecutive non-expanding {} groups
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2026-13149). Fix: Update that package to its patched version.
  • Worth fixing GHSA-832h-xg76-4gv6 ReDoS in brace-expansion
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2017-18077). Fix: Update that package to its patched version.
  • Worth fixing GHSA-f886-m6hf-6m8v brace-expansion: Zero-step sequence causes process hang and memory exhaustion
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2026-33750). Fix: Update that package to its patched version.
  • Worth fixing GHSA-mh99-v99m-4gvg brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2026-14257). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rgw5-rvv9-x895 brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2026-69152). Fix: Update that package to its patched version.
  • Worth fixing GHSA-9vvw-cc9w-f27h debug Inefficient Regular Expression Complexity vulnerability
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2017-20165). Fix: Update that package to its patched version.
  • Worth fixing GHSA-9vvw-cc9w-f27h debug Inefficient Regular Expression Complexity vulnerability
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2017-20165). Fix: Update that package to its patched version.
  • Worth fixing GHSA-jmr9-qjv8-65gv extract-zip unvalidated symlink path traversal
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2026-56876). Fix: Update that package to its patched version.
  • Worth fixing GHSA-hmw2-7cc7-3qxx form-data: CRLF injection in form-data via unescaped multipart field names and filenames
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2026-12143). Fix: Update that package to its patched version.
  • Worth fixing GHSA-xf7w-r453-m56c Arbitrary File Overwrite in fstream
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2019-13173). Fix: Update that package to its patched version.
  • Worth fixing GHSA-44pw-h2cw-w3vq Uncontrolled Resource Consumption in Hawk
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2022-29167). Fix: Update that package to its patched version.
  • Worth fixing GHSA-c429-5p7v-vgjp hoek subject to prototype pollution via the clone function.
    /workdirs/scan-f57811dd-dd0c-48e3-885d-ace7595ae270/yarn.lock
    A package you depend on has a known security hole (CVE-2020-36604). Fix: Update that package to its patched version.
… 75 more not shown

via OSV-Scanner v1.9.2 · Apache-2.0

Risky code patterns — Semgrep none found ✓

Code that can be exploited: injection, hardcoded credentials and similar.

Nothing found by this check. ✓

via Semgrep v1.147.0 · LGPL-2.1

Malicious dependencies — Guarddog 1 found

Packages that look intentionally malicious: typosquats, sneaky install scripts.

  • Worth fixing guarddog-npm-npm-install-script npm-install-script match in electron-prebuilt 1.4.13
    electron-prebuilt
    A dependency shows signs of being intentionally malicious (typosquat, hidden install script, etc.). Fix: Don’t install it until you’ve verified the package. Consider removing it.

via Guarddog v2.10.0 · Apache-2.0

Project health

A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.

Project health — OpenSSF Scorecard didn’t run

Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OpenSSF Scorecard · Apache-2.0

About these results. Six open-source checks ran in parallel; every finding is tagged with the tool that produced it. The verdict follows a published rule. False positives and false negatives are normal — a clean scan does not mean the code is secure, and a red verdict does not mean the project is compromised.