gitsafehub
github.com/realorangeone/git-mirror ↗

realorangeone/git-mirror

scanned 2026-08-14 · git 40063da
3 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 dependencies1Known OSS vulnerabilities5Risky code patterns✓Malicious dependencies1Project 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ⓘ 1 found

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

  • Worth fixing CVE-2024-3772 python-pydantic: regular expression denial of service via crafted email string
    requirements.txt
    A package you depend on has a known security hole (CVE-2024-3772). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

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

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious PYSEC-2026-2120 Black is the uncompromising Python code formatter. Black provides a GitHub action for formatting code. This action supports an option, use_pyproject: true, for reading the version of Black to use from
    /workdirs/scan-d31c172d-c97b-4a28-acde-5662fec63f86/dev-requirements.txt
    A package you depend on has a known security hole (CVE-2026-31900). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2024-48 Versions of the package black before 24.3.0 are vulnerable to Regular Expression Denial of Service (ReDoS) via the lines_with_leading_tabs_expanded function in the strings.py file. An attacker could e
    /workdirs/scan-d31c172d-c97b-4a28-acde-5662fec63f86/dev-requirements.txt
    A package you depend on has a known security hole (CVE-2024-21503). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2121 Black is the uncompromising Python code formatter. Prior to 26.3.1, Black writes a cache file, the name of which is computed from various formatting options. The value of the --python-cell-magics opti
    /workdirs/scan-d31c172d-c97b-4a28-acde-5662fec63f86/dev-requirements.txt
    A package you depend on has a known security hole (CVE-2026-32274). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1812 Pydantic regular expression denial of service
    /workdirs/scan-d31c172d-c97b-4a28-acde-5662fec63f86/dev-requirements.txt
    A package you depend on has a known security hole (CVE-2024-3772). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1812 Pydantic regular expression denial of service
    /workdirs/scan-d31c172d-c97b-4a28-acde-5662fec63f86/requirements.txt
    A package you depend on has a known security hole (CVE-2024-3772). 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ⓘ 1 found · 1 serious

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

  • Serious guarddog-pypi-code-execution code-execution match in coloredlogs 15.0
    coloredlogs
    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.