Here is a little bit more background:

Docs

The mapped_column() construct in modern Python is normally augmented by the use of PEP 484 Python type annotations, where it is capable of deriving its column-configuration information from type annotations associated with the attribute as declared in the Declarative mapped class. These type annotations, if used, must be present within a special SQLAlchemy type called Mapped, which is a generic type that indicates a specific Python type within it.

-- https://docs.sqlalchemy.org/en/20/orm/declarative_tables.html#orm-annotated-declarative-automated-mapping-with-type-annotations

Both forms are used in the examples ( tagged as Annotated Example and Non-Annotated Example).

The Non-Annotated form is also a natural migration step to SQLAlchemy 2.0:

Users of 1.x SQLAlchemy will note the use of the mapped_column() construct, which is new as of the SQLAlchemy 2.0 series. This ORM-specific construct is intended first and foremost to be a drop-in replacement for the use of Column within Declarative mappings only, adding new ORM-specific convenience features such as the ability to establish mapped_column.deferred within the construct, and most importantly to indicate to typing tools such as Mypy and Pylance an accurate representation of how the attribute will behave at runtime at both the class level as well as the instance level. As will be seen in the following sections, it’s also at the forefront of a new annotation-driven configuration style introduced in SQLAlchemy 2.0.

-- https://docs.sqlalchemy.org/en/20/orm/declarative_tables.html#orm-annotated-declarative-automated-mapping-with-type-annotations

Personal Background

In a codebase I am working with, in some places the annotations were missing (for whatever reason). We were not aware that these columns were treated as Any causing some bugs in the past.

I'd suggest collecting all the SQAlchemy 2.0 specific rules into the SA2 prefix, so making this SA201 rather than SA001. That way we leave the door open to put generally useful rules into SA0 and legacy rules into SA1, making it easier to read through the rules once there are more of them.