gitsafehub
github.com/yaroslav/yandex_inflect ↗

yaroslav/yandex_inflect

scanned 2026-08-15 · git b561b2e
2 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 secrets✓Vulnerable dependencies5Known OSS vulnerabilities5Risky 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ⓘ 5 found

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

  • Worth fixing CVE-2013-1801 httparty Gem for Ruby Type Casting Parameter Parsing Remote Code Execution
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2013-1801). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-68696 httparty: Httparty: Server-Side Request Forgery (SSRF) allows information disclosure and unauthorized internal access.
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2025-68696). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-22049 httparty before 0.21.0 is vulnerable to an assumed-immutable web param ...
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2024-22049). Fix: Update that package to its patched version.
  • Worth fixing CVE-2013-0175 multi_xml Gem for Ruby XML Parameter Parsing Remote Command Execution
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2013-0175). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-8130 rake: OS Command Injection via egrep in Rake::FileList
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2020-8130). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 5 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-5pq7-52mg-hr42 httparty has multipart/form-data request tampering vulnerability
    /workdirs/scan-901beac1-799c-469e-81c5-f66132a32796/Gemfile.lock
    A package you depend on has a known security hole (CVE-2024-22049). Fix: Update that package to its patched version.
  • Worth fixing GHSA-hm5p-x4rq-38w4 httparty Has Potential SSRF Vulnerability That Leads to API Key Leakage
    /workdirs/scan-901beac1-799c-469e-81c5-f66132a32796/Gemfile.lock
    A package you depend on has a known security hole (CVE-2025-68696). Fix: Update that package to its patched version.
  • Worth fixing GHSA-mgx3-27hr-mfgp HTTParty does not restrict casts of string values
    /workdirs/scan-901beac1-799c-469e-81c5-f66132a32796/Gemfile.lock
    A package you depend on has a known security hole (CVE-2013-1801). Fix: Update that package to its patched version.
  • Worth fixing GHSA-pchc-949f-53m5 Improper Input Validation in multi_xml
    /workdirs/scan-901beac1-799c-469e-81c5-f66132a32796/Gemfile.lock
    A package you depend on has a known security hole (CVE-2013-0175). Fix: Update that package to its patched version.
  • Worth fixing GHSA-jppv-gw3r-w3q8 OS Command Injection in Rake
    /workdirs/scan-901beac1-799c-469e-81c5-f66132a32796/Gemfile.lock
    A package you depend on has a known security hole (CVE-2020-8130). 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.