More screenshots
Works with the AI Agents you already use
Streamlit and Gradio App Check
Check Streamlit and Gradio apps before you deploy: secrets.toml that git would commit, user input rendered as HTML or run with eval, Gradio paths that expose the disk, API keys in code, public launches without login.
$5
Streamlit and Gradio App Check
Example session with this skill installed
Check this project with streamlit-gradio-app-check.
- Read your context and instructions
- Compiled the streamlit and gradio
$ python3 scripts/check_data_app.py examples/risky
BLOCK .streamlit/secrets.toml:2 D01 SECRETS_TOML_NOT_IGNORED
No .gitignore rule covers this file. It holds 2 secret values: HF_TOKEN, connections.notes_db.password.
Why: secrets.toml holds real secret values (API keys, passwords, connection passwords, the [auth] client_secret or cookie_secret) and no .gitignore rule covers it, so git add . commits it. Streamlit's docs say to add this file to .gitignore. Anyone with the repository, a fork or a copy of the Space can use these secrets.
Safer: Add .streamlit/secrets.toml to .gitignore (git rm --cached it if it was committed), rotate the secrets it held, give the deployed app its secrets in the host's secrets settings, and commit a secrets.toml.example with placeholders instead.
BLOCK app.py:8 D05 LITERAL_API_KEY
BLOCK app.py:18 D02 USER_INPUT_RENDERED_AS_HTML
BLOCK app.py:21 D02 USER_INPUT_RENDERED_AS_HTML
BLOCK app.py:24 D04 USER_INPUT_RUN_AS_CODE
BLOCK app.py:28 D04 USER_INPUT_RUN_AS_CODE
BLOCK app.py:29 D04 USER_INPUT_RUN_AS_CODE
BLOCK support_bot.py:7 D04 USER_INPUT_RUN_AS_CODE
BLOCK support_bot.py:27 D03 GRADIO_ALLOWED_PATHS_TOO_BROAD
REVIEW .streamlit/config.toml:3 D12 XSRF_PROTECTION_OFF
REVIEW .streamlit/config.toml:4 D13 CORS_PROTECTION_OFF
REVIEW .streamlit/config.toml:7 D15 ERROR_DETAILS_SHOWN
REVIEW Dockerfile:7 D12 XSRF_PROTECTION_OFF
REVIEW app.py:12 D18 PASSWORD_IN_CODE
REVIEW app.py:15 D17 SECRET_SHOWN_IN_PAGE
REVIEW app.py:26 D14 UPLOAD_WITHOUT_TYPE_LIMIT
REVIEW support_bot.py:17 D16 HTML_SANITIZER_OFF
REVIEW support_bot.py:19 D14 UPLOAD_WITHOUT_TYPE_LIMIT
REVIEW support_bot.py:24 D11 PUBLIC_LAUNCH_WITHOUT_AUTH
REVIEW support_bot.py:25 D15 ERROR_DETAILS_SHOWN
REVIEW support_bot.py:26 D13 CORS_PROTECTION_OFF
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 5 files, 5 with Streamlit or Gradio content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
st.markdown(f"<h2>Notes for {name}</h2>", unsafe_allow_html=True) puts whatever a visitor types into your page as HTML, and demo.launch(share=True, allowed_paths=["/"]) lets anyone with the link download any file on your machine. This skill finds those and the other Streamlit and Gradio mistakes listed below before you deploy or share the app, and tells you how to fix each one.
Your agent runs a scanner on your app's Python files (those that import streamlit or gradio), .streamlit/config.toml, secrets.toml, and the Dockerfiles, Procfiles, compose files and shell scripts that start the app. It follows values that come from visitors (input widgets, query parameters, uploaded files, the signed-in user's name, the session-state keys that widgets and chat history fill, the free-text arguments of Gradio event handlers) through assignments and into the file's own helper functions. It treats Gradio Dropdown, Radio, Slider and Number values as fixed choices, recognises fixes such as html.escape, shlex.quote, ast.literal_eval and lookups in a constant table, follows import aliases such as import subprocess as sp, reads your .gitignore files to see whether secrets.toml is kept out of git, and knows the Streamlit and Gradio defaults (XSRF and CORS protection on, st.html sanitized, Gradio bound to 127.0.0.1 with strict CORS and chat sanitizing on). It never runs your app or connects anywhere. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- D01: a secrets.toml holding real keys or passwords that no .gitignore rule covers
- D02: visitor input rendered as HTML with unsafe_allow_html=True, st.html with JavaScript allowed, st.iframe or the deprecated st.components.v1.html
- D03: Gradio allowed_paths, set_static_paths or GRADIO_ALLOWED_PATHS that include the disk root, a drive root, the home folder, /home, /Users, /root or /etc
- D04: visitor input reaching eval, exec, compile, a shell command, or a pickle-style loader (pickle, joblib, dill, cloudpickle, pandas.read_pickle and similar)
- D05: API keys and secrets written in app code, config.toml or run files (provider key formats, random-looking values under secret names, passwords in database URLs)
REVIEW
- D11: Gradio launch(share=True) or server_name="0.0.0.0" without auth or auth_dependency
- D12: Streamlit XSRF protection turned off, or its cookie sent cross-site
- D13: Streamlit enableCORS = false or Gradio strict_cors=False
- D14: uploads without a type limit (st.file_uploader without type, Gradio file inputs without file_types)
- D15: error details shown to visitors (Gradio show_error=True, an explicit Streamlit showErrorDetails of full or stacktrace)
- D16: Gradio sanitize_html=False on a Chatbot or Markdown
- D17: st.secrets, a secret or a whole section from it, or the process environment (including getenv of a key) shown on the page
- D18: login passwords written in code (Gradio auth tuples, password == "..." checks, password variables)
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official documentation link for each rule
- A risky and a safe example project, and the real report the scanner produces on the risky one
Limits It reads each file on its own and follows values in straight-line order: values passed between modules, kept on class attributes or built in branches are not followed, Gradio handlers given as class methods or through functools.partial are not followed, and Python files that import neither Streamlit nor Gradio are not checked. Gradio gr.HTML output is not checked, because Gradio does not document whether it sanitizes it. It reads .gitignore files but not git history, so a secrets.toml committed before it was ignored is not detected. Settings made in a hosting dashboard (Streamlit Community Cloud, Hugging Face Spaces) are not visible. Gradio debug=True is not reported, because it only keeps the script running. NOT FLAGGED is not a guarantee.
Static check of file text. Values passed between modules, Gradio gr.HTML output, git history and settings made in a hosting dashboard are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert values (NOTREAL..., not-a-real-...) for the scanner to find. Nothing in it is run.