gitsafehub
github.com/proxyee-down-org/proxyee-down ↗

proxyee-down-org/proxyee-down

scanned 2026-05-28 · git a8f1709
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 dependencies16Known OSS vulnerabilities8Risky 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ⓘ 16 found

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

  • Worth fixing CVE-2017-18640 snakeyaml: Billion laughs attack via alias feature
    main/pom.xml
    A package you depend on has a known security hole (CVE-2017-18640). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-1471 SnakeYaml: Constructor Deserialization Remote Code Execution
    main/pom.xml
    A package you depend on has a known security hole (CVE-2022-1471). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-25857 snakeyaml: Denial of Service due to missing nested depth limitation for collections
    main/pom.xml
    A package you depend on has a known security hole (CVE-2022-25857). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-38749 snakeyaml: Uncaught exception in org.yaml.snakeyaml.composer.Composer.composeSequenceNode
    main/pom.xml
    A package you depend on has a known security hole (CVE-2022-38749). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-38750 snakeyaml: Uncaught exception in org.yaml.snakeyaml.constructor.BaseConstructor.constructObject
    main/pom.xml
    A package you depend on has a known security hole (CVE-2022-38750). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-38751 snakeyaml: Uncaught exception in java.base/java.util.regex.Pattern$Ques.match
    main/pom.xml
    A package you depend on has a known security hole (CVE-2022-38751). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-38752 snakeyaml: Uncaught exception in java.base/java.util.ArrayList.hashCode
    main/pom.xml
    A package you depend on has a known security hole (CVE-2022-38752). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-41854 dev-java/snakeyaml: DoS via stack overflow
    main/pom.xml
    A package you depend on has a known security hole (CVE-2022-41854). Fix: Update that package to its patched version.
  • Worth fixing CVE-2017-18640 snakeyaml: Billion laughs attack via alias feature
    pom.xml
    A package you depend on has a known security hole (CVE-2017-18640). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-1471 SnakeYaml: Constructor Deserialization Remote Code Execution
    pom.xml
    A package you depend on has a known security hole (CVE-2022-1471). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-25857 snakeyaml: Denial of Service due to missing nested depth limitation for collections
    pom.xml
    A package you depend on has a known security hole (CVE-2022-25857). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-38749 snakeyaml: Uncaught exception in org.yaml.snakeyaml.composer.Composer.composeSequenceNode
    pom.xml
    A package you depend on has a known security hole (CVE-2022-38749). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-38750 snakeyaml: Uncaught exception in org.yaml.snakeyaml.constructor.BaseConstructor.constructObject
    pom.xml
    A package you depend on has a known security hole (CVE-2022-38750). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-38751 snakeyaml: Uncaught exception in java.base/java.util.regex.Pattern$Ques.match
    pom.xml
    A package you depend on has a known security hole (CVE-2022-38751). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-38752 snakeyaml: Uncaught exception in java.base/java.util.ArrayList.hashCode
    pom.xml
    A package you depend on has a known security hole (CVE-2022-38752). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-41854 dev-java/snakeyaml: DoS via stack overflow
    pom.xml
    A package you depend on has a known security hole (CVE-2022-41854). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 8 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-3mc7-4q67-w48m Uncontrolled Resource Consumption in snakeyaml
    /workdirs/scan-0e6cd06e-f722-4242-9510-240a524d3607/main/pom.xml
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-mjmj-j48q-9wg2 SnakeYaml Constructor Deserialization Remote Code Execution
    /workdirs/scan-0e6cd06e-f722-4242-9510-240a524d3607/main/pom.xml
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-rvwf-54qp-4r6v SnakeYAML Entity Expansion during load operation
    /workdirs/scan-0e6cd06e-f722-4242-9510-240a524d3607/main/pom.xml
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI GHSA-98wm-3w3q-mw94 snakeYAML before 1.31 vulnerable to Denial of Service due to Out-of-bounds Write
    /workdirs/scan-0e6cd06e-f722-4242-9510-240a524d3607/main/pom.xml
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI GHSA-9w3m-gqgf-c4p9 snakeYAML before 1.32 vulnerable to Denial of Service due to Out-of-bounds Write
    /workdirs/scan-0e6cd06e-f722-4242-9510-240a524d3607/main/pom.xml
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI GHSA-c4r9-r8fh-9vj2 snakeYAML before 1.31 vulnerable to Denial of Service due to Out-of-bounds Write
    /workdirs/scan-0e6cd06e-f722-4242-9510-240a524d3607/main/pom.xml
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI GHSA-hhhw-99gj-p3c3 snakeYAML before 1.31 vulnerable to Denial of Service due to Out-of-bounds Write
    /workdirs/scan-0e6cd06e-f722-4242-9510-240a524d3607/main/pom.xml
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI GHSA-w37g-rhq8-7m4j Snakeyaml vulnerable to Stack overflow leading to denial of service
    /workdirs/scan-0e6cd06e-f722-4242-9510-240a524d3607/main/pom.xml
    A package you depend on has a known security hole. 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: 2.0/10
    A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
  • Minor scorecard-CI-Tests CI-Tests scored 0: 0 out of 4 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-Maintained Maintained scored 0: project is archived
    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-Signed-Releases Signed-Releases scored 0: Project has not signed or included provenance with any releases.
    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.