FastAPI Production Engineering

PassAudited by ClawScan on May 1, 2026.

Overview

This is an instruction-only FastAPI engineering guide that does not install code, request credentials, or show suspicious behavior in the provided artifacts.

This skill appears safe to install as an instruction-only engineering guide. Before using it on a real project, review any generated files or configuration changes, especially authentication, secrets, CORS, database, Docker, and CI/CD settings.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

The agent may generate or modify project files, auth patterns, Docker configuration, or CI setup when you ask it to use this skill.

Why it was flagged

The skill is designed to guide changes to application code and deployment configuration. That is consistent with its stated purpose, but those changes can affect a real service if applied without review.

Skill content
`set up a new FastAPI project` — full structure + config; `add authentication` — JWT + dependency injection pattern; `prepare for production` — Dockerfile + CI + checklist
Recommendation

Apply it only to the intended project, review generated diffs, and validate auth, secrets, CORS, Docker, and CI settings before deploying.

What this means

Projects generated from this guidance will need sensitive application secrets such as database connection strings and JWT secrets.

Why it was flagged

The skill includes application patterns for database and JWT secrets. The guidance uses environment-based `SecretStr` fields and says not to hardcode secrets, so this appears purpose-aligned rather than suspicious.

Skill content
database_url: SecretStr  # Required — no default ... jwt_secret: SecretStr  # Required ... model_config = {"env_file": ".env", "env_file_encoding": "utf-8"}
Recommendation

Store real secrets in a proper secrets manager or protected environment variables, avoid committing `.env` files, and rotate any credentials accidentally exposed during development.