typescript-any
Explicit 'any' type defeats TypeScript's type safety
Applies to: TypeScript
Why this matters
Using 'any' disables TypeScript's type checking for that value, allowing bugs to slip through that the compiler would otherwise catch. It's a common beginner pattern to reach for 'any' when types get complicated, but it undermines the entire benefit of using TypeScript. Use 'unknown' if you truly don't know the type, or define proper interfaces.
Catch it before it ships
pip install stablestack # or: npx stablestackstablestack # scans your project, TYPE008 includedstablestack explain TYPE008TYPE008 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: TYPE008
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.
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