gitsafehub
github.com/jasongrout/mybinder.org-user-guide ↗

jasongrout/mybinder.org-user-guide

scanned 2026-08-11 · git 5c229d7
1 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 dependencies✓Known OSS vulnerabilities11Risky 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ⓘ none found ✓

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

Nothing found by this check. ✓

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 11 found · 1 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious PYSEC-2026-348 h11 accepts some malformed Chunked-Encoding bodies
    /workdirs/scan-101973ea-72ec-4c22-9b68-7d138b135038/docs/requirements.txt
    A package you depend on has a known security hole (CVE-2025-43859). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2017-74 The tqdm._version module in tqdm versions 4.4.1 and 4.10 allows local users to execute arbitrary code via a crafted repo with a malicious git log in the current working directory.
    /workdirs/scan-101973ea-72ec-4c22-9b68-7d138b135038/docs/requirements.txt
    A package you depend on has a known security hole (CVE-2016-10075). 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-101973ea-72ec-4c22-9b68-7d138b135038/docs/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-183 pyjwt v2.10.1 was discovered to contain weak encryption. NOTE: this is disputed by the Supplier because the key length is chosen by the application that uses the library (admittedly, library users may
    /workdirs/scan-101973ea-72ec-4c22-9b68-7d138b135038/docs/requirements.txt
    A package you depend on has a known security hole (CVE-2025-45768). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-120 PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array li
    /workdirs/scan-101973ea-72ec-4c22-9b68-7d138b135038/docs/requirements.txt
    A package you depend on has a known security hole (CVE-2026-32597). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-175 PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient passes its uri argument directly to urllib.request.urlopen() which uses Python stdlib's default OpenerDirector register
    /workdirs/scan-101973ea-72ec-4c22-9b68-7d138b135038/docs/requirements.txt
    A package you depend on has a known security hole (CVE-2026-48522). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-176 PyJWT is a JSON Web Token implementation in Python. From 2.9.0 to 2.12.1, there is a verifier-side algorithm allow-list bypass when jwt.decode() or jwt.decode_complete() are called with a PyJWK key. T
    /workdirs/scan-101973ea-72ec-4c22-9b68-7d138b135038/docs/requirements.txt
    A package you depend on has a known security hole (CVE-2026-48523). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-178 PyJWT is a JSON Web Token implementation in Python. From 2.8.0 to 2.12.1, when verifying detached JWS tokens using the unencoded-payload option ("b64": false, RFC 7797), PyJWT performs Base64URL decod
    /workdirs/scan-101973ea-72ec-4c22-9b68-7d138b135038/docs/requirements.txt
    A package you depend on has a known security hole (CVE-2026-48525). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-179 PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, when the verifier is decoding JSON Web Tokens, while supporting both asymmetric and HMAC algorithms, the library does not validate
    /workdirs/scan-101973ea-72ec-4c22-9b68-7d138b135038/docs/requirements.txt
    A package you depend on has a known security hole (CVE-2026-48526). Fix: Update that package to its patched version.
  • Minor PYSEC-2026-1976 tqdm CLI arguments injection attack
    /workdirs/scan-101973ea-72ec-4c22-9b68-7d138b135038/docs/requirements.txt
    A package you depend on has a known security hole (CVE-2024-34062). Fix: Update that package to its patched version.
  • Minor PYSEC-2026-177 PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient.get_signing_key() forces a fresh HTTP request to the JWKS endpoint for every JWT with an unknown kid value, with no rat
    /workdirs/scan-101973ea-72ec-4c22-9b68-7d138b135038/docs/requirements.txt
    A package you depend on has a known security hole (CVE-2026-48524). 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.