Package Transfer Policy

This document describes how ownership of a public package on Hex changes hands: between owners who agree, when an owner lost access to their account, and for packages whose owners can't be reached. It also covers reports of name squatting and misleading names. Private packages belong to their organization, whose administrators manage them, and can't be transferred.

Transferring a package you own

Owners at the full level can add and remove owners on the package's owners page or with mix hex.owner. Owners at the maintainer level can publish releases but can't manage owners. To hand a package over, transfer it on the owners page or with mix hex.owner transfer. A transfer makes the new owner the package's only owner.

Only add owners you trust. A new owner can publish releases that everyone who depends on the package installs when they update.

If you lost access to your account

The Hex team doesn't restore access to accounts, as described in the Account Recovery Policy, and doesn't move packages to a new account on proof of identity either. Ask another owner at the full level of the package to add your new account. If you were the only owner at the full level, the package can only change hands as described in Packages whose owners can't be reached.

Packages whose owners can't be reached

You can ask to take over a package if both of the following are true:

  1. No release of the package has been published in the past 12 months.
  2. None of the package's owners respond to you or to the Hex team.

Try to contact the owners yourself first, using the email addresses on the owners' user pages. If no address is shown or they don't respond, email support@hex.pm with the package name, how you have tried to reach the owners, what you plan to do with the package, and why a fork under a different name doesn't work for you.

The Hex team then contacts every owner at least three times over six weeks, using the email addresses on their accounts. For an owner that is an organization, we contact the organization's administrators. An owner who agrees transfers the package themselves on the owners page, and we don't transfer a package because of an email reply. If an owner objects, we don't transfer the package under this section.

If no owner responds, the Hex team decides whether to transfer the package. We are more reluctant to transfer packages that many other packages depend on, and in those cases we usually recommend a fork under a different name.

A former owner at the full level who lost a package this way can ask for it back from their account within one year of the transfer, and we will return it.

After a transfer

A transfer doesn't change the releases published before it. A public release can only be replaced within one hour of being published, or within 24 hours of the package being created, and a transfer doesn't extend that. Like any owner, the new owner can publish new releases, retire releases and publish documentation. The transfer is recorded in the package's audit log.

Name squatting and misleading names

If you think a package exists only to reserve a name, or has a name that is intentionally confusing or misleading, report it with "Report package" on the package's page. Explain why the package violates the Code of Conduct or the Terms of Service. We may remove such packages.

User and organization names

We are unlikely to transfer a user or organization name. Having a user or organization that has never published a package is valid, and they may own private packages that we can't disclose. Contact the user or organization directly and CC support@hex.pm. We may consider a transfer in special circumstances.

If you believe a package or its name infringes your copyright or trademark, follow the Copyright Policy.

Changes

This is a living document and may be updated from time to time. Please refer to the git history for this document to view the changes.