What problem does it solve?
Security risks at API boundaries, secret handling, and environment management create exposure that can lead to data theft, service disruption, and compliance gaps. This Skill provides a structured checklist and guidelines to enforce secure defaults across code, configuration, and deployments.
Core Features & Use Cases
- Secret Management: Never commit secrets to git. Secrets belong in env files (gitignored); use pydantic-settings to load secrets and validate on startup; avoid reading os.environ directly.
- Env Safety Checklist: Ensure env files are in gitignore; env example files contain placeholders only; no secrets in pyproject.toml, CI configs, or source code; audit git history for secret leakage.
- API Boundaries & Gatekeeping (Future): Validate inputs with models, apply rate limits, use CORS allowlists, and return generic errors to clients.
- Authentication (Future): Prefer server-side sessions and protected routes; align with role-based access control for environments.
- Dependency Auditing: Run pip-audit periodically; pin major versions; review dependency changelogs before upgrades.
- Code Review Security Flags: Flag hardcoded secrets, SQL/NoSQL injection vectors, unvalidated input, overly permissive CORS, and logging of sensitive data.
- OpsSec Practices: Safe retrieval of external assets, dependency guard, HTML sanitization, and caution with commands that modify files or networks; audit for safety.
Quick Start
Run a security review to validate API boundaries, secret handling, env safety, and dependency auditing.