T08 · Insecure Dependencies
- Location
SKILL.md:180- Finding
Unpinned Dependency Installation Creates Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only FastAPI skill with some insecure production examples users should harden before copying.
Install only as general FastAPI reference material. Before using its snippets in real services, replace the JWT secret with secure secret management, avoid returning raw exception details from health endpoints, pin and review dependencies, and check any outbound HTTP examples for sensitive data exposure.
SKILL.md:180Unpinned Dependency Installation Creates Supply-Chain Risk
SKILL.md:195Readiness Endpoint Exposes Internal Exception Details
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
return users
# Use def for: psycopg2, pymongo, requests (blocking libs)
# FastAPI automatically runs def endpoints in a threadpool
@app.get('/users/sync')
def get_users_sync():
return sync_db.query('SELECT * FROM users')
The JWT example is presented as a production authentication pattern but hard-codes SECRET_KEY = "your-secret-key", which can normalize insecure secret handling and lead users to deploy weak or default keys. In an auth context, a predictable or copied secret can allow token forgery and authentication bypass if reused in real deployments.
This markdown skill teaches OAuth2/JWT handling and later shows outbound HTTP requests, but the document does not warn users about protecting secret keys, avoiding hardcoded credentials, or the privacy implications of sending data to external services. Under the markdown-specific warning rule, examples that affect privacy or system integrity should include some disclosure or cautionary note.
No suspicious patterns detected.