inline-type-definition
Inline type definition instead of using shared/generated types.
Applies to: JavaScript, TypeScript
Why this matters
When frontend and backend define the same types separately, they can drift apart. Use generated types from OpenAPI/GraphQL schemas or a shared types package. Inline type definitions like `{ user_id: string, name: string }` should be replaced with imported types that stay in sync with your API.
Catch it before it ships
pip install stablestack # or: npx stablestackstablestack # scans your project, TYPE005 includedstablestack explain TYPE005TYPE005 is part of the Pro rule set. See pricing — the free tier ships 24 checks with no signup.
False positive in your codebase? Suppress a single line with # noqa: TYPE005
More Type Safety checks
weak-typing
Weak typing pattern (Dict[str, Any], List[Any]) loses type safety.
TYPE002naked-dict-for-structured-data
Using plain dict for structured data instead of dataclass/TypedDict.
TYPE004missing-type-hints
Function is missing type hints.
TYPE006dict-type-inconsistency
Dict return type annotation doesn't match actual value types being assigned.
TYPE007duplicate-type-definition
Type definition may be duplicated across files.
TYPE008typescript-any
Explicit 'any' type defeats TypeScript's type safety
TYPE009env-non-null-assertion
Non-null assertion on env vars can cause runtime crashes
TYPE010unsafe-json-parse
JSON parsing with type assertion lacks runtime validation