gitsafehub
github.com/changcheng967/rps-bot ↗

changcheng967/rps-bot

scanned 2026-08-07 · git f3819d1
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 secrets3Vulnerable dependenciesKnown OSS vulnerabilities9Risky code patternsMalicious dependenciesProject health

Security checks

Leaked secrets — Gitleaks 3 found · 3 serious

API keys, passwords or tokens committed into the repo.

  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    index.html:88
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    index.html:96
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    index.html:83
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivy couldn’t run

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

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

via Trivy v0.70.0 · Apache-2.0

error: unexpected fault address 0x7ff65db0a000 fatal error: fault [signal SIGBUS: bus error code=0x2 addr=0x7ff65db0a000 pc=0x93c06a] goroutine 1 gp=0xc000002380 m=5 mp=0xc000580008 [running]: runtime.throw({0x57e6c1e?, 0x0?}) /opt/hostedtoolcache/go/1.25.9/x64/src/runtime/panic.go:1094 +0x48 fp=0xc00118

Known OSS vulnerabilities — OSV-Scanner 9 found · 1 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious PYSEC-2026-1486 Keras Directory Traversal Vulnerability
    /workdirs/scan-e5b111fa-640b-4767-8bde-54e6146689db/requirements.txt
    A package you depend on has a known security hole (CVE-2025-12060). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2151 Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Us
    /workdirs/scan-e5b111fa-640b-4767-8bde-54e6146689db/requirements.txt
    A package you depend on has a known security hole (CVE-2026-27205). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-215 Internationalized Domain Names in Applications (IDNA) for Python provides support for Internationalized Domain Names in Applications (IDNA) and Unicode IDNA Compatibility Processing. In versions prior
    /workdirs/scan-e5b111fa-640b-4767-8bde-54e6146689db/requirements.txt
    A package you depend on has a known security hole (CVE-2026-45409). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-121 An issue in keras 3.7.0 allows attackers to write arbitrary files to the user's machine via downloading a crafted tar file through the get_file function.
    /workdirs/scan-e5b111fa-640b-4767-8bde-54e6146689db/requirements.txt
    A package you depend on has a known security hole (CVE-2024-55459). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1487 Keras is vulnerable to arbitrary local file loading and Server-Side Request Forgery
    /workdirs/scan-e5b111fa-640b-4767-8bde-54e6146689db/requirements.txt
    A package you depend on has a known security hole (CVE-2025-12058). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2324 Keras versions prior to 3.14.0 are vulnerable to a path traversal issue in the archive extraction utilities located in `keras/src/utils/file_utils.py`. The functions `filter_safe_tarinfos()` and `filt
    /workdirs/scan-e5b111fa-640b-4767-8bde-54e6146689db/requirements.txt
    A package you depend on has a known security hole (CVE-2026-11816). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2547 Keras has an untrusted deserialization vulnerability
    /workdirs/scan-e5b111fa-640b-4767-8bde-54e6146689db/requirements.txt
    A package you depend on has a known security hole (CVE-2026-1462). Fix: Update that package to its patched version.
  • Worth fixing GHSA-36fq-jgmw-4r9c Keras is vulnerable to Deserialization of Untrusted Data
    /workdirs/scan-e5b111fa-640b-4767-8bde-54e6146689db/requirements.txt
    A package you depend on has a known security hole (CVE-2025-9906). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1805 protobuf affected by a JSON recursion depth bypass
    /workdirs/scan-e5b111fa-640b-4767-8bde-54e6146689db/requirements.txt
    A package you depend on has a known security hole (CVE-2026-0994). 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.