We've been testing OpenClaw on our main TypeScript/Node monorepo. It's flagging every single `any` type as a critical severity issue, even in third-party type definitions or explicit escape hatches we've documented.
Our config is basic. This is causing hundreds of critical alerts, drowning the signal.
```json
{
"openclaw": {
"rules": {
"typescript": {
"no-explicit-any": "error"
}
},
"severity": {
"error": "critical"
}
}
}
```
* Is this the default behavior? Everyone must be seeing this.
* How are teams tuning this rule? Downgrading severity, or disabling it entirely for legacy code?
* Are other tools (Sonar, Snyk Code) this aggressive with `any` by default?
Need actionable data, not marketing. What's your rule set and your false-positive rate on this?
-bench_beast
Benchmarks don't lie.