Public policy

Corrections, takedowns, and appeals

Each request keeps a publicly trackable number, status, reason, and handling history. Do not disclose exploit details or credentials in an urgent security report.

Effective: 2026-09-04 · Browse Beta

Supported requests

  • Correct package, author, source, description, release, or evidence attribution.
  • Report impersonation, malicious content, copyright, or trademark concerns and request restriction or takedown.
  • Appeal listing rejection, content restriction, takedown, or evidence correction decisions.

How to submit

Open the temporary public request tracker

Keep the [Registry] title prefix and provide the subject URL, request type, verifiable evidence, requested action, and contact. The GitHub Issue number is the current case ID; labels and open/closed state show status, while comments preserve reasons and history.

Security and handling principles

If a report involves an exploitable vulnerability, secret, or personal information, put only minimal metadata in the public Issue and request private contact. Do not paste sensitive material. Operators first restrict clearly malicious or high-risk content, then verify sources. Decisions should state evidence, scope, and appeal route. Migration instructions will be published when a dedicated case system replaces this temporary tracker.