api-audit

To detect type drift, audit API routes and shared types by cross-referencing Fastify route schemas against shared type definitions. This analysis surfaces missing validations, type mismatches, and auth gaps to guide remediation.

Static analysis for API route mismatches catalogs routes, plugins, and shared type definitions to detect inconsistencies. It generates a cross-reference report highlighting missing validations and auth gaps without modifying the source code.

Audit API routes for missing validations by running a static analysis across route files, plugins, and shared schemas. This enforces read-only analysis to surface type drift and authentication gaps, producing a findings report.

Yes, you can cross-reference Fastify plugins against shared schemas using a read-only audit. The analysis enforces no changes to source code, generating a cross-reference of route schemas against shared definitions to identify mismatches.

Yes, API route auditing works with shared type definitions in separate packages by cataloging schemas under packages/types/ and cross-referencing them against route files under apps/api/src/routes/ to detect drift and missing validations.

The limitation of read-only static analysis for API routes is that it enforces no changes to source code. It only catalogs routes and shared types to surface missing validations, type drift, and auth gaps without applying remediation.