gitsafehub
github.com/kenjis/monkey-patch ↗

kenjis/monkey-patch

scanned 2026-08-09 · git 3301c70
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 dependencies4Known OSS vulnerabilities4Risky 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ⓘ 4 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
    vendor-bin/tools/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-24765 phpunit: PHPUnit: Arbitrary code execution via unsafe deserialization of code coverage files
    vendor-bin/tools/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 CVE-2026-67434 OS Command injection
    vendor-bin/tools/composer.lock
    A package you depend on has a known security hole (CVE-2026-67434). 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
    vendor-bin/tools/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ⓘ 4 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-vvj3-c3rp-c85p PHPUnit Vulnerable to Unsafe Deserialization in PHPT Code Coverage Handling
    /workdirs/scan-7c8edcb9-2189-4ed3-8d30-f7071e2ffac8/vendor-bin/tools/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-hmqg-cxww-wqhq PHP_CodeSniffer gitblame report command injection via crafted filename
    /workdirs/scan-7c8edcb9-2189-4ed3-8d30-f7071e2ffac8/vendor-bin/tools/composer.lock
    A package you depend on has a known security hole (CVE-2026-67434). 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-7c8edcb9-2189-4ed3-8d30-f7071e2ffac8/vendor-bin/tools/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-7c8edcb9-2189-4ed3-8d30-f7071e2ffac8/vendor-bin/tools/composer.lock
    A package you depend on has a known security hole (CVE-2026-24739). 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.