More screenshots
Works with the AI Agents you already use
Python Requirements Safety Check
Check requirements.txt for supply-chain risks: http package indexes, tokens in index URLs, --trusted-host, --extra-index-url dependency confusion, unpinned versions, git branches and URLs without hashes.
$5
Python Requirements Safety Check
Example session with this skill installed
Check this project with python-requirements-safety-check.
- Read your context and instructions
- Compiled the python requirements safety
$ python3 scripts/check_requirements.py examples/risky
BLOCK requirements.txt:2 Q01 DOWNLOAD_OVER_HTTP
--index-url http://pypi.example.com/simple
Why: A package index, find-links page or package URL uses plain http://, so anyone on the network path can swap the package for their own code during install.
Safer: Use https:// for every index and package URL.
BLOCK requirements.txt:3 Q02 CREDENTIALS_IN_URL
BLOCK requirements.txt:4 Q03 TRUSTED_HOST
REVIEW requirements.txt:3 Q11 EXTRA_INDEX_URL
REVIEW requirements.txt:5 Q17 PARTIAL_HASHES
REVIEW requirements.txt:6 Q12 UNPINNED_REQUIREMENT
REVIEW requirements.txt:9 Q15 DUPLICATE_REQUIREMENT
REVIEW requirements.txt:10 Q13 VCS_NOT_PINNED
REVIEW requirements.txt:11 Q14 URL_WITHOUT_HASH
REVIEW requirements.txt:12 Q16 LOCAL_PATH_REQUIREMENT
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 1 file, 1 with requirements 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
--extra-index-url makes pip take the highest version from either index, so a public package with your private package's name can win. This skill finds that and nine other requirements-file risks, and tells you how to fix each one.
Your agent runs a scanner on requirements*.txt, requirements*.in and constraints files. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Tokens in URLs are never printed.
What it checks
BLOCK
- Q01: an index or package URL over plain http://
- Q02: a username, password or token in a URL
- Q03: --trusted-host
REVIEW
- Q11: --extra-index-url
- Q12: a requirement not pinned with == (ranges are fine in .in files)
- Q13: a git dependency not pinned to a commit
- Q14: a direct URL with no hash
- Q15: the same package listed twice
- Q16: editable or local path installs
- Q17: only some lines have --hash
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example, and the real report the scanner produces on the risky one
Limits It reads requirements files as text. It does not read pyproject.toml, Pipfile or lock files, resolve dependencies, or check vulnerability databases. NOT FLAGGED is not a guarantee.
Reads requirements-style files only (not pyproject.toml, Pipfile or lock files) and does not resolve dependencies. 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 5 days ago
Requires
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example file includes a clearly fake, inert token (not-a-real-token) for the scanner to find.