forge-validation

Validate HTTP request bodies and query params by parsing them against explicit schemas at the trust boundary. This ensures untrusted inputs are rejected before use, returning structured 400 field-level errors on failure instead of ad-hoc checks.

Environment variable validation at startup requires parsing against a single-source schema to establish a strict trust boundary. This guarantees that your application boots only with correctly typed and formatted environment configurations.

Ensure type safety for queue payloads and API responses by deriving types directly from a single-source validation schema. This provides typed guarantees so your code can trust the validated shapes of external data without manual checks.

Validate file uploads safely by enforcing strict size limits and sniffing file bytes rather than trusting client-provided headers. This format safety mechanism prevents disguised payloads from bypassing your input validation boundaries.

You can return structured field-level errors by replacing ad-hoc checks with schema-based validation. This provides stable, client-actionable error details including specific per-field paths and codes rather than generic failures.

You need schema validation for API error handling whenever processing external data like HTTP bodies, queue payloads, or third-party responses. It prevents untrusted input handling failures by enforcing strict size and format constraints at every boundary.