repeated-dict-key-assignment
Three or more consecutive string-key assignments to the same dict — the dict has structure that should be a typed shape.
Applies to: Python
Why this matters
A run of `d['name'] = name; d['email'] = email; d['age'] = age` treats the dict as if it were a struct, but with no type checking. Fat-finger any key (typo, copy-paste mistake, schema drift) and the bug is silent until runtime. A TypedDict, @dataclass, or Pydantic model gives the same shape with IDE / pyright support and a single named place to update when the shape changes.
Catch it before it ships
pip install stablestack # or: npx stablestackstablestack # scans your project, TYPE016 includedstablestack explain TYPE016TYPE016 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: TYPE016
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