gitsafehub
github.com/adamdehaven/firacode ↗

adamdehaven/firacode

scanned 2026-08-12 · git 415c773
1 of 6 checks flagged a security issue
🟡 Worth a look
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secretsVulnerable dependenciesKnown OSS vulnerabilities11Risky code patternsMalicious dependenciesProject 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 none found ✓

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

Nothing found by this check. ✓

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 11 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing PYSEC-2026-215 Internationalized Domain Names in Applications (IDNA) for Python provides support for Internationalized Domain Names in Applications (IDNA) and Unicode IDNA Compatibility Processing. In versions prior
    /workdirs/scan-b3b2225d-cb0d-4ae5-ba8f-95d8df3fb366/googlefonts-qa/scripts/requirements.txt
    A package you depend on has a known security hole (CVE-2026-45409). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2020-173 The pip package before 19.2 for Python allows Directory Traversal when a URL is given in an install command, because a Content-Disposition header can have ../ in a filename, as demonstrated by overwri
    /workdirs/scan-b3b2225d-cb0d-4ae5-ba8f-95d8df3fb366/googlefonts-qa/scripts/requirements.txt
    A package you depend on has a known security hole (CVE-2019-20916). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2021-437 A flaw was found in python-pip in the way it handled Unicode separators in git references. A remote attacker could possibly use this issue to install a different revision on a repository. The highest
    /workdirs/scan-b3b2225d-cb0d-4ae5-ba8f-95d8df3fb366/googlefonts-qa/scripts/requirements.txt
    A package you depend on has a known security hole (CVE-2021-3572). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2023-228 When installing a package from a Mercurial VCS URL (ie "pip install hg+...") with pip prior to v23.3, the specified Mercurial revision could be used to inject arbitrary configuration options to the
    /workdirs/scan-b3b2225d-cb0d-4ae5-ba8f-95d8df3fb366/googlefonts-qa/scripts/requirements.txt
    A package you depend on has a known security hole (CVE-2023-5752). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1795 pip's fallback tar extraction doesn't check symbolic links point to extraction directory
    /workdirs/scan-b3b2225d-cb0d-4ae5-ba8f-95d8df3fb366/googlefonts-qa/scripts/requirements.txt
    A package you depend on has a known security hole (CVE-2025-8869). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-196 pip would treat console_scripts and gui_scripts as paths instead of file names without sanitizing the resolved absolute path to the installation directory, leading to entry points being installed outs
    /workdirs/scan-b3b2225d-cb0d-4ae5-ba8f-95d8df3fb366/googlefonts-qa/scripts/requirements.txt
    A package you depend on has a known security hole (CVE-2026-8643). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2875 pip has an interpretation conflict due to handling both concatenated tar and ZIP files as ZIP files
    /workdirs/scan-b3b2225d-cb0d-4ae5-ba8f-95d8df3fb366/googlefonts-qa/scripts/requirements.txt
    A package you depend on has a known security hole (CVE-2026-3219). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2876 pip Vulnerable to Inclusion of Functionality from Untrusted Control Sphere
    /workdirs/scan-b3b2225d-cb0d-4ae5-ba8f-95d8df3fb366/googlefonts-qa/scripts/requirements.txt
    A package you depend on has a known security hole (CVE-2026-6357). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2023-117 A ReDoS issue was discovered in pygments/lexers/smithy.py in pygments through 2.15.0 via SmithyLexer.
    /workdirs/scan-b3b2225d-cb0d-4ae5-ba8f-95d8df3fb366/googlefonts-qa/scripts/requirements.txt
    A package you depend on has a known security hole (CVE-2022-40896). Fix: Update that package to its patched version.
  • Minor PYSEC-2026-1796 pip Path Traversal vulnerability
    /workdirs/scan-b3b2225d-cb0d-4ae5-ba8f-95d8df3fb366/googlefonts-qa/scripts/requirements.txt
    A package you depend on has a known security hole (CVE-2026-1703). Fix: Update that package to its patched version.
  • Minor PYSEC-2026-2987 Pygments has Regular Expression Denial of Service (ReDoS) due to Inefficient Regex for GUID Matching
    /workdirs/scan-b3b2225d-cb0d-4ae5-ba8f-95d8df3fb366/googlefonts-qa/scripts/requirements.txt
    A package you depend on has a known security hole (CVE-2026-4539). 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.