cross-language-type-duplication
Type defined in both Python and TypeScript — likely drift target
Applies to: Python, TypeScript
Why this matters
When the same shape lives as a hand-written Pydantic model AND a hand-written TS type / interface, the two drift the moment one side adds a field. Pick one source of truth (usually Python) and code-gen the other. Mark the generated file with `generated-types` in its name so this rule knows to ignore it.
Catch it before it ships
pip install stablestack # or: npx stablestackstablestack # scans your project, TYPE015 includedstablestack explain TYPE015TYPE015 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: TYPE015
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.
TYPE005inline-type-definition
Inline type definition instead of using shared/generated types.
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