gitsafehub
github.com/Hacker0x01/fluent_logger_rails ↗

Hacker0x01/fluent_logger_rails

scanned 2026-05-31 · git daf2ee8
2 of 6 checks flagged a security issue
🟡 Worth a look
6 checks ran. Start with vulnerable dependencies below.

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

Leaked secrets✓Vulnerable dependencies4Known OSS vulnerabilities4Risky code patterns✓Malicious dependencies✓Project health9

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

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

  • Worth fixing CVE-2026-33176 Rails: Active Support: Active Support: Denial of Service via large scientific notation strings
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-33176). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-38037 rubygem-activesupport: File Disclosure of Locally Encrypted Files
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2023-38037). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-33169 rails: rails-activesupport: Active Support: Denial of Service via crafted long digit strings
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-33169). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-33170 Rails: Active Support: Active Support: Cross-Site Scripting (XSS) due to improper HTML safety flag propagation in SafeBuffer#%
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-33170). 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-2j26-frm8-cmj9 Rails Active Support has a possible DoS vulnerability in its number helpers
    /workdirs/scan-0cd522d2-c2d0-4d79-98e3-a59f09190bc5/Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-33176). Fix: Update that package to its patched version.
  • Worth fixing GHSA-89vf-4333-qx8v Rails Active Support has a possible XSS vulnerability in SafeBuffer#%
    /workdirs/scan-0cd522d2-c2d0-4d79-98e3-a59f09190bc5/Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-33170). Fix: Update that package to its patched version.
  • Worth fixing GHSA-cg4j-q9v8-6v38 Rails Active Support has a possible ReDoS vulnerability in number_to_delimited
    /workdirs/scan-0cd522d2-c2d0-4d79-98e3-a59f09190bc5/Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-33169). Fix: Update that package to its patched version.
  • Worth fixing GHSA-cr5q-6q9f-rq6q Active Support Possibly Discloses Locally Encrypted Files
    /workdirs/scan-0cd522d2-c2d0-4d79-98e3-a59f09190bc5/Gemfile.lock
    A package you depend on has a known security hole (CVE-2023-38037). 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ⓘ 9 notes

Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.

  • Worth fixing scorecard-overall OpenSSF Scorecard overall: 3.1/10
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-CI-Tests CI-Tests scored 0: 1 out of 11 merged PRs checked by a CI test -- score normalized to 0
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-CII-Best-Practices CII-Best-Practices scored 0: no effort to earn an OpenSSF best practices badge detected
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-Dependency-Update-Tool Dependency-Update-Tool scored 0: no update tool detected
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-Fuzzing Fuzzing scored 0: project is not fuzzed
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-Pinned-Dependencies Pinned-Dependencies scored 0: dependency not pinned by hash detected -- score normalized to 0
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-SAST SAST scored 0: SAST tool is not run on all commits -- score normalized to 0
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-Security-Policy Security-Policy scored 0: security policy file not detected
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
  • Minor scorecard-Token-Permissions Token-Permissions scored 0: detected GitHub workflow tokens with excessive permissions
    A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.

via OpenSSF Scorecard v5.5.0 · 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.