gitsafehub
github.com/seldaek/composer ↗

seldaek/composer

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

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

Leaked secrets—Vulnerable dependencies2Known OSS vulnerabilities7Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ timed out

API keys, passwords or tokens committed into the repo.

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

via Gitleaks v8.21.2 · MIT

error: timeout after 120s

Vulnerable dependencies — Trivyⓘ 2 found · 1 serious

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

  • Serious CVE-2024-51736 CVE-2024-51736: Command execution hijack on Windows with Process class
    composer.lock
    A package you depend on has a known security hole (CVE-2024-51736). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-24739 Symfony's incorrect argument escaping under MSYS2/Git Bash can lead to destructive file operations on Windows
    composer.lock
    A package you depend on has a known security hole (CVE-2026-24739). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

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

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious GHSA-r7c9-c69m-rph8 Code Injection in PHPUnit
    /workdirs/scan-65a18bde-5032-4e6d-bb8e-e03895b59157/composer.lock
    A package you depend on has a known security hole (CVE-2017-9841). Fix: Update that package to its patched version.
  • Worth fixing GHSA-vvj3-c3rp-c85p PHPUnit Vulnerable to Unsafe Deserialization in PHPT Code Coverage Handling
    /workdirs/scan-65a18bde-5032-4e6d-bb8e-e03895b59157/composer.lock
    A package you depend on has a known security hole (CVE-2026-24765). Fix: Update that package to its patched version.
  • Worth fixing GHSA-qq5c-677p-737q Symfony vulnerable to command execution hijack on Windows with Process class
    /workdirs/scan-65a18bde-5032-4e6d-bb8e-e03895b59157/composer.lock
    A package you depend on has a known security hole (CVE-2024-51736). Fix: Update that package to its patched version.
  • Worth fixing GHSA-r39x-jcww-82v6 Symfony's incorrect argument escaping under MSYS2/Git Bash can lead to destructive file operations on Windows
    /workdirs/scan-65a18bde-5032-4e6d-bb8e-e03895b59157/composer.lock
    A package you depend on has a known security hole (CVE-2026-24739). Fix: Update that package to its patched version.
  • Minor GHSA-4qpc-3hr4-r2p4 Symfony's YAML Parser Vulnerable to Exponential Memory Allocation via Recursive Collection-Alias Expansion ("Billion Laughs")
    /workdirs/scan-65a18bde-5032-4e6d-bb8e-e03895b59157/composer.lock
    A package you depend on has a known security hole (CVE-2026-45304). Fix: Update that package to its patched version.
  • Minor GHSA-9frc-8383-795m Symfony's YAML Parser has a ReDoS via Catastrophic Backtracking in Parser::cleanup() Regex
    /workdirs/scan-65a18bde-5032-4e6d-bb8e-e03895b59157/composer.lock
    A package you depend on has a known security hole (CVE-2026-45305). Fix: Update that package to its patched version.
  • Minor GHSA-c2p3-7m5p-cv8x Symfony hardened the parser when handling untrusted input
    /workdirs/scan-65a18bde-5032-4e6d-bb8e-e03895b59157/composer.lock
    A package you depend on has a known security hole (CVE-2026-45133). 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.