Before You File a Bug Report Please Confirm You Have Done The Following...

• I have tried restarting my IDE and the issue persists.
• I have updated to the latest version of the packages.
• I havesearched for related issues and found none that matched my issue.
• I haveread the FAQ and my problem is not listed.

Playground Link

https://typescript-eslint.io/play/#ts=5.7.2&fileType=.tsx&code=CYUwxgNghgTiAEYD2A7AzgF3lFIQC5sUBPAbgCgc9s14AmUoA&eslintrc=N4KABGBEBOCuA2BTAzpAXGUEKQAIBcBPABxQGNoBLY-AWhXkoDt8B6Jge1tieQEMAZolpFStPsmSJo%2BShybooAdz7QF4MAF8QmoA&tsconfig=N4KABGBEDGD2C2AHAlgGwKYCcDyiAuysAdgM6QBcYoEEkJemy0eAcgK6qoDCAFutAGsylBm3TgwAXxCSgA&tokens=false

Repro Code

declareconstanee:any;aneeas2;

ESLint Config

module.exports={"rules":{"@typescript-eslint/no-unsafe-type-assertion":"warn"}}

tsconfig

{"compilerOptions": {"strictNullChecks":true  }}

Expected Result

Unsafetype assertion fromany detected: consider using type guards or a safertype assertion. 2:1 - 2:10

Actual Result

Unsafecast fromany detected: consider using type guards or a safercast. 2:1 - 2:10

Additional Info

Thedocs for no-unsafe-type-assertion, as well asthe TS docs on type assertions, are careful not to use the word "cast" since, in other programming languages, that generally can imply runtime behavior. Note that this idea is reinforced by the naming of the core ruleno-extra-boolean-cast.

I propose: let's avoid using the word "cast" entirely.