PyPI is considering a mechanism to reserve package name prefixes for organizations following the adoption of PEP 752 in June 2026. The proposal aims to link recognizable prefixes such as google-cloud-, opentelemetry-, and apache-airflow-providers- to verified owners, reducing the risk of name squatting and dependency confusion attacks.
Currently, PyPI treats all package names as independent entries in a flat namespace. Organizations like yandex-bot and seznam-bot have published hundreds of placeholder packages to protect prefixes, yet any user can still register new names that begin with familiar strings. PEP 752 introduces implicit namespaces so that control over a prefix automatically covers future packages matching the normalized name pattern.
Normalization rules mean that google.cloud.storage would fall under a reserved google-cloud- prefix, while google-cloudstorage would not. Projects matching an existing prefix but published by unauthorized accounts would receive a 409 Conflict error on upload. Existing packages retain the ability to publish new versions under grandfathering rules.
Data from CodeScoring covering more than 800,000 active projects reveals that no examined prefix belongs to a single owner. The aws- prefix is controlled by 743 accounts, google- by 484, and types- by 68. Even within narrower prefixes such as datasette-, multiple independent maintainers publish plugins.
The upcoming PEP 755 will define the application process. Only organization accounts may apply, prefixes must exceed three characters and already be in use by the applicant, and overly generic terms will be rejected. Large open-source projects, universities, and government entities may receive fee waivers, while paid organizations could receive faster review.
Unlike npm scoped packages, the Python approach keeps the flat namespace intact to avoid breaking existing tooling and dependency files. New metadata will allow clients and corporate proxies to enforce prefix ownership policies once support is added.
