unguard 0.12.0 → 0.13.0

package/README.md

@@ -145,8 +145,17 @@ These rules use the TypeScript type checker. Non-nullable types suppress the dia
 
 | Rule | Severity | What it catches |
 | ---- | -------- | --------------- |
+| `no-inline-param-type` | warning | `(params: { id: string; ... })` — inline object type on parameter |
 | `prefer-default-param-value` | info | Optional param reassigned with `??` in the body |
 | `prefer-required-param-with-guard` | info | `arg?: T` followed by `if (!arg) throw` |
+| `repeated-literal-property` | warning | Same literal value (`as const`: 3+, plain: 5+) repeated in object properties within a file |
+| `repeated-return-shape` | warning | 3+ functions return object literals with the same property name set |
+
+### State management
+
+| Rule | Severity | What it catches |
+| ---- | -------- | --------------- |
+| `no-module-state-write` | warning | Function mutates a module-scope binding (`count++`, `state.ready = ...`, `cache.set(...)`) |
 
 ### Cross-file analysis
 
@@ -186,6 +195,15 @@ type AnyNode = Record<string, any>;
 file.ts:2:31 error Explicit `any` annotation ... (intentional escape hatch for untyped AST access)
 ```
 
+For `warning` and `info` diagnostics, you can explicitly mark a finding as intentional with `@unguard <rule-id>` on the same line or immediately above:
+
+```typescript
+// @unguard no-module-state-write module cache is intentional in this adapter
+cache.set(user.id, user);
+```
+
+`@unguard` never suppresses `error` diagnostics.
+
 ## API
 
 ```typescript