BSK-0152 analyze

Missing type stubs for installed package

Fires when a package is imported and resolves to a .py source file (not .pyi) without a py.typed marker. This means the package is installed but lacks type information, reducing type safety. This rule is off by default — the default configuration is pure PEP conformance — and a project opts in with an explicit BSK-0152 severity. Once enabled, an untyped third-party import is a hard error; a project can soften it per import (# type: warningBSK-0152) or globally ("BSK-0152" = "warning") to use non-type-safe libraries at its own risk.

import flask  # E0152: Package 'flask' is installed but has no type stubs

How to handle it

This Basilisk-specific rule is off by default. Enable its stubs tag when the policy fits your project, then configure its severity globally or per path in pyproject.toml.

Canonical URL: https://www.basilisk-python.dev/errors/BSK-0152