-
Notifications
You must be signed in to change notification settings - Fork 0
add official PyPI package-docs lookup #6
Copy link
Copy link
Open
Labels
area:package-ecosystemPyPI/package metadata and package docs coveragePyPI/package metadata and package docs coveragecomplianceSecurity/compliance-driven behavior or trust boundariesSecurity/compliance-driven behavior or trust boundariesenhancementNew feature or requestNew feature or requestpriority:P2Medium priorityMedium priority
Milestone
Metadata
Metadata
Assignees
Labels
area:package-ecosystemPyPI/package metadata and package docs coveragePyPI/package metadata and package docs coveragecomplianceSecurity/compliance-driven behavior or trust boundariesSecurity/compliance-driven behavior or trust boundariesenhancementNew feature or requestNew feature or requestpriority:P2Medium priorityMedium priority
Summary
Add package-docs lookup for official PyPI packages / package documentation.
Motivation
Today the server is intentionally stdlib-only, which keeps the trust/compliance story very clean. But in practice, many teams will immediately ask for package-level docs once they adopt the Python stdlib flow.
The request here is to expand beyond stdlib with a still-controlled scope:
Why this matters
For real development workflows, stdlib-only coverage is useful but incomplete. A lot of day-to-day engineering work happens in package ecosystems, and users will naturally want a compliant path there too.
Expected behavior
A future package-docs mode could:
Non-goal / caution
The value of this project comes from its clean trust boundary, so this should not become a generic web search tool.
If implemented, the feature should keep strong rules around:
Open design question
This may be better as:
Either way, the compliance model should stay obvious and auditable.