No implicit any types

Implicit any is TypeScript's escape hatch — every untyped function parameter defaults to any, which propagates through the call chain and silently disables type checking for all downstream code that touches it. ISO 25010:2011 §6.5.4 classifies this as a maintainability defect. When noImplicitAny is off, a renamed field in an API response or database schema causes zero compile-time errors and surfaces only as a runtime crash or silent data corruption in production.

Re-enable noImplicitAny (or use strict: true) and add explicit type annotations. Use unknown when the type is genuinely unknown at compile time — never any as a shortcut — then narrow at the callsite.

// Bad: implicit any causes noImplicitAny error:
function transform(value) { return value.toString(); }

// Good: explicit type:
function transform(value: string): string { return value.toString(); }

// Good: unknown + runtime narrowing:
function parsePayload(raw: unknown): MyType {
  if (!isMyType(raw)) throw new Error('Unexpected shape');
  return raw;
}