gitsafehub
github.com/pypa/gh-action-pip-audit ↗

pypa/gh-action-pip-audit

scanned 2026-08-15 · git fb241f5
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 dependencies3Known OSS vulnerabilities14Risky 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ⓘ 3 found · 3 serious

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

  • Serious CVE-2019-20477 PyYAML: command execution through python/object/apply constructor in FullLoader
    test/pylock/pylock.toml
    A package you depend on has a known security hole (CVE-2019-20477). Fix: Update that package to its patched version.
  • Serious CVE-2020-14343 PyYAML: incomplete fix for CVE-2020-1747
    test/pylock/pylock.toml
    A package you depend on has a known security hole (CVE-2020-14343). Fix: Update that package to its patched version.
  • Serious CVE-2020-1747 PyYAML: arbitrary command execution through python/object/new when FullLoader is used
    test/pylock/pylock.toml
    A package you depend on has a known security hole (CVE-2020-1747). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 14 found · 3 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious PYSEC-2020-176 PyYAML 5.1 through 5.1.2 has insufficient restrictions on the load and load_all functions because of a class deserialization issue, e.g., Popen is a class in the subprocess module. NOTE: this issue ex
    /workdirs/scan-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/test/pylock/pylock.toml
    A package you depend on has a known security hole (CVE-2019-20477). Fix: Update that package to its patched version.
  • Serious PYSEC-2020-96 A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method o
    /workdirs/scan-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/test/pylock/pylock.toml
    A package you depend on has a known security hole (CVE-2020-1747). Fix: Update that package to its patched version.
  • Serious PYSEC-2021-142 A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or
    /workdirs/scan-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/test/pylock/pylock.toml
    A package you depend on has a known security hole (CVE-2020-14343). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1374 filelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLock
    /workdirs/scan-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/requirements.txt
    A package you depend on has a known security hole (CVE-2026-22701). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1375 filelock has a TOCTOU race condition which allows symlink attacks during lock file creation
    /workdirs/scan-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/requirements.txt
    A package you depend on has a known security hole (CVE-2025-68146). Fix: Update that package to its patched version.
  • 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-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/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-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/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-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/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-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/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-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/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-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/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-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/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-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/requirements.txt
    A package you depend on has a known security hole (CVE-2026-6357). Fix: Update that package to its patched version.
  • Minor PYSEC-2026-1796 pip Path Traversal vulnerability
    /workdirs/scan-21139e57-9259-4ddc-a6ec-c5bbe5d6be9c/requirements.txt
    A package you depend on has a known security hole (CVE-2026-1703). 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.