gitsafehub
github.com/popcor255/keycloak-pkce ↗

popcor255/keycloak-pkce

scanned 2026-08-14 · git 638811a
2 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 secrets✓Vulnerable dependencies10Known OSS vulnerabilities8Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ none found ✓

API keys, passwords or tokens committed into the repo.

Nothing found by this check. ✓

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 10 found · 1 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.
  • 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-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-2022-0235 node-fetch: exposure of sensitive information to an unauthorized actor
    yarn.lock
    A package you depend on has a known security hole (CVE-2022-0235). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-3803 nodejs-nth-check: inefficient regular expression complexity
    yarn.lock
    A package you depend on has a known security hole (CVE-2021-3803). Fix: Update that package to its patched version.
  • Minor CVE-2020-15168 node-fetch: size of data after fetch() JS thread leads to DoS
    yarn.lock
    A package you depend on has a known security hole (CVE-2020-15168). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 8 found · 1 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious GHSA-jf85-cpcp-j695 Prototype Pollution in lodash
    /workdirs/scan-efac0a37-568a-4ff0-a410-123874dc011d/yarn.lock
    A package you depend on has a known security hole (CVE-2019-10744). Fix: Update that package to its patched version.
  • Worth fixing GHSA-29mw-wpgm-hmr9 Regular Expression Denial of Service (ReDoS) in lodash
    /workdirs/scan-efac0a37-568a-4ff0-a410-123874dc011d/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 GHSA-35jh-r3h4-6jhm Command Injection in lodash
    /workdirs/scan-efac0a37-568a-4ff0-a410-123874dc011d/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 GHSA-f23m-r3pf-42rh lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`
    /workdirs/scan-efac0a37-568a-4ff0-a410-123874dc011d/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 GHSA-p6mc-m468-83gw Prototype Pollution in lodash
    /workdirs/scan-efac0a37-568a-4ff0-a410-123874dc011d/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 GHSA-r683-j2x4-v87g node-fetch forwards secure headers to untrusted sites
    /workdirs/scan-efac0a37-568a-4ff0-a410-123874dc011d/yarn.lock
    A package you depend on has a known security hole (CVE-2022-0235). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rp65-9cf3-cjxr Inefficient Regular Expression Complexity in nth-check
    /workdirs/scan-efac0a37-568a-4ff0-a410-123874dc011d/yarn.lock
    A package you depend on has a known security hole (CVE-2021-3803). Fix: Update that package to its patched version.
  • Minor GHSA-w7rc-rwvf-8q5r The `size` option isn't honored after following a redirect in node-fetch
    /workdirs/scan-efac0a37-568a-4ff0-a410-123874dc011d/yarn.lock
    A package you depend on has a known security hole (CVE-2020-15168). Fix: Update that package to its patched version.

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ⓘ none found ✓

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

Nothing found by this check. ✓

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.