typeshed_source_user_managed analyze

A custom typeshed folder is user-managed: you supply its license and contents, so typeshed's license terms are not applied to it

When you point Basilisk at a custom typeshed-path folder, Basilisk treats it as user-managed: you supply both its contents and its license. Basilisk does not attach python/typeshed's license terms to a tree it did not vet.

This advisory makes that explicit so you never unintentionally rely on a custom tree believing it carries typeshed's license, or skip the pin and content verification that the bundled and pinned sources enforce.

It composes with typeshed_source_unpinned — a custom folder is both unpinned and user-managed. Grade it like any rule:

[tool.basilisk.rules]
"typeshed_source_user_managed" = "warning"   # or "off" to silence

It is reported out of band (CLI banner, Server Info, MCP status), never as a Python diagnostic, so it can never affect conformance.

Canonical documentation

• python/typeshed
• Basilisk configuration: typeshed source

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/typeshed_source_user_managed