Informational scan, not a security audit. How this is computed.
API keys, passwords or tokens committed into the repo.
This check didn’t finish — that’s not the same as “clean.” Try Check again above.
Packages you depend on that have known security holes (CVEs).
CVE-2023-6572 Gradio Exposure of Sensitive Information to an Unauthorized Actor vulnerabilityCVE-2024-1728 Gradio allows users to access arbitrary filesCVE-2025-23042 Gradio Blocked Path ACL Bypass VulnerabilityCVE-2023-6730 transformers has a Deserialization of Untrusted Data vulnerabilityCVE-2023-51449 Gradio makes the `/file` secure against file traversal and server-side request forgery attacksCVE-2024-0964 Gradio Path Traversal vulnerabilityCVE-2024-1561 gradio vulnerable to Path TraversalCVE-2024-2206 gradio Server-Side Request Forgery vulnerabilityCVE-2024-34510 Gradio allows credential leakage on WindowsCVE-2024-47084 Gradios's CORS origin validation is not performed when the request has a cookieCVE-2024-47867 Gradio lacks integrity checking on the downloaded FRP clientCVE-2024-47870 Gradio has a race condition in update_root_in_config may redirect user trafficCVE-2024-47871 Gradio uses insecure communication between the FRP client and serverCVE-2024-4941 Local file inclusion in gradioCVE-2026-28414 Gradio is Vulnerable to Absolute Path Traversal on Windows with Python 3.13+CVE-2026-28416 Gradio: Gradio: Server-Side Request Forgery allows access to internal services via malicious Space loadingCVE-2026-48545 Gradio contains a cookie injection vulnerabilityCVE-2024-1183 gradio Server-Side Request Forgery vulnerabilityCVE-2024-1727 Gradio applications running locally vulnerable to 3rd party websites accessing routes and uploading filesCVE-2024-1729 Gradio apps vulnerable to timing attacks to guess passwordCVE-2024-47164 Gradio's `is_in_or_equal` function may be bypassedCVE-2024-47165 Gradio's CORS origin validation accepts the null originCVE-2024-47166 Gradio has a one-level read path traversal in `/custom_component`CVE-2024-47167 Gradio vulnerable to SSRF in the path parameter of /queue/joinCVE-2024-47868 Gradio has several components with post-process steps allow arbitrary file leaksYour dependencies cross-checked against the OSV vulnerability database.
PYSEC-2023-255 Command Injection in GitHub repository gradio-app/gradio prior to main.PYSEC-2024-215 Gradio is an open-source Python package designed for quick prototyping. This vulnerability relates to **Server-Side Request Forgery (SSRF)** in the `/queue/join` endpoint. Gradio’s `async_save_url_to_PYSEC-2024-219 Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves **insecure communication** between the FRP (Fast Reverse Proxy) client and server when Gradio's `shaPYSEC-2024-274 Gradio v4.36.1 was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py. This vulnerability is triggered via a crafted input. NOTE: the supplier disputes thPYSEC-2024-321 A command injection vulnerability exists in the gradio-app/gradio repository, specifically within the 'test-functional.yml' workflow. The vulnerability arises due to improper neutralization of specialPYSEC-2025-118 Gradio is an open-source Python package that allows quick building of demos and web application for machine learning models, API, or any arbitrary Python function. Gradio's Access Control List (ACL) fPYSEC-2026-345 Gradio allows users to access arbitrary filesPYSEC-2023-300 Deserialization of Untrusted Data in GitHub repository huggingface/transformers prior to 4.36.PYSEC-2026-2290 A vulnerability in the LightGlue model loading path of huggingface/transformers version 5.2.0 allows an attacker-controlled model repository to execute arbitrary code during model initialization. The PYSEC-2026-2161 GitPython is a python library used to interact with Git repositories. Prior to version 3.1.47, _clone() validates multi_options as the original list, then executes shlex.split(" ".join(multi_options))PYSEC-2026-457 Arbitrary Code Execution in PillowPYSEC-2023-255 Command Injection in GitHub repository gradio-app/gradio prior to main.PYSEC-2024-215 Gradio is an open-source Python package designed for quick prototyping. This vulnerability relates to **Server-Side Request Forgery (SSRF)** in the `/queue/join` endpoint. Gradio’s `async_save_url_to_PYSEC-2024-219 Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves **insecure communication** between the FRP (Fast Reverse Proxy) client and server when Gradio's `shaPYSEC-2024-274 Gradio v4.36.1 was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py. This vulnerability is triggered via a crafted input. NOTE: the supplier disputes thPYSEC-2024-321 A command injection vulnerability exists in the gradio-app/gradio repository, specifically within the 'test-functional.yml' workflow. The vulnerability arises due to improper neutralization of specialPYSEC-2025-118 Gradio is an open-source Python package that allows quick building of demos and web application for machine learning models, API, or any arbitrary Python function. Gradio's Access Control List (ACL) fPYSEC-2026-345 Gradio allows users to access arbitrary filesPYSEC-2026-507 PyTorch Lightning path traversal vulnerabilityPYSEC-2023-300 Deserialization of Untrusted Data in GitHub repository huggingface/transformers prior to 4.36.PYSEC-2026-2290 A vulnerability in the LightGlue model loading path of huggingface/transformers version 5.2.0 allows an attacker-controlled model repository to execute arbitrary code during model initialization. The PYSEC-2026-1845 pytest has vulnerable tmpdir handlingPYSEC-2018-28 The Requests package before 2.20.0 for Python sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to disPYSEC-2023-74 Requests is a HTTP library. Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use `rePYSEC-2026-1872 Requests vulnerable to .netrc credentials leak via malicious URLsCode that can be exploited: injection, hardcoded credentials and similar.
Nothing found by this check. ✓
Packages that look intentionally malicious: typosquats, sneaky install scripts.
This check didn’t finish — that’s not the same as “clean.” Try Check again above.
A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.
Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.
scorecard-overall OpenSSF Scorecard overall: 3.2/10scorecard-CI-Tests CI-Tests scored 0: 0 out of 12 merged PRs checked by a CI test -- score normalized to 0scorecard-CII-Best-Practices CII-Best-Practices scored 0: no effort to earn an OpenSSF best practices badge detectedscorecard-Dependency-Update-Tool Dependency-Update-Tool scored 0: no update tool detectedscorecard-Fuzzing Fuzzing scored 0: project is not fuzzedscorecard-Maintained Maintained scored 0: 0 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 0scorecard-Pinned-Dependencies Pinned-Dependencies scored 0: dependency not pinned by hash detected -- score normalized to 0scorecard-SAST SAST scored 0: SAST tool is not run on all commits -- score normalized to 0scorecard-Security-Policy Security-Policy scored 0: security policy file not detectedscorecard-Signed-Releases Signed-Releases scored 0: Project has not signed or included provenance with any releases.scorecard-Token-Permissions Token-Permissions scored 0: detected GitHub workflow tokens with excessive permissions