Docs menuNames and verified domains

Names and verified domains

Last updated: November 20, 2026

Every LPM.dev package name starts with the name of its owner: @lpm.dev/<owner>.<package>. The owner is a username or an organization slug. Usernames and organization slugs share one set of names. This page explains which names LPM.dev protects, how a company or a project gets its own name, and when a name can move to another owner.

Verified domains

An owner can verify one domain with a DNS TXT record. LPM.dev Registry then shows the domain on the owner's profile, package pages, and package cards. The domain tells you that the owner controls the domain's DNS records. LPM checks the record about once a day.

A verified domain never changes a package name, and it gives no access to anything. If an owner loses its domain, its packages install as before. Verified domains explains how to verify one.

Protected names

LPM.dev protects three kinds of names:

  • Names that no account or organization can have, such as npm, node, core, and google.
  • Company and project names on a reviewed list, such as stripe and vercel. Only an organization of the company or the project can get one of these names, after a request.
  • The npm usernames of the maintainers of popular npm packages. The npm user can get the name by proving the npm account. npm usernames explains how.

An owner that had a name before LPM.dev protected it keeps the name. LPM.dev adds company and project names to the list when a company or a project asks, and it can remove a name from the list later. A name that LPM.dev grants to an owner stays with that owner.

Request a company or project name

A company or project name goes only to an organization. A username cannot get one. If you make a product alone, create an organization for the product and request the name for it.

  1. Open the organization's "Settings" and then "Verification". The request is under "Brand name".
  2. Enter the name and select "Start request".
  3. Prove control of the brand. Verify one of the brand's domains, or connect the LPM GitHub App to one of the brand's GitHub organizations. You must be an admin of the GitHub organization, and your GitHub account must be linked to LPM.dev.
  4. If the brand has a domain, make sure that an owner of the organization has a confirmed email address at that domain. If the brand has no domain, commit the line that the page shows to lpm-name-request.txt on the default branch of the GitHub organization's public .github repository.
  5. Select "Check proofs", and then select "Submit for review".

Request the name before the organization publishes its first package. After the first publish, the name of the organization cannot change. If the organization already published, request the name for a new organization.

An organization that proved a brand can request the brand's other names for another organization. You must be an owner of the organization that takes the name, and an owner or an admin of the organization that proved the brand.

How LPM.dev reviews a request

LPM.dev reviews every request. Nothing is approved automatically. While a request waits, the name stays protected for everyone.

The reviewer reads each proof again when the review starts:

  • The domain is still verified, and its registration matches the registration that LPM.dev recorded when it listed the brand.
  • The requester is still an admin of the GitHub organization, and the LPM GitHub App is still installed on it.
  • The requester is still an owner or an admin of the organization.

A domain that is less than one year old, a domain without a registration date, or a domain whose registration changed gets a closer review. LPM.dev does not approve a request while its proofs fail, or after the registry confirms that its domain is no longer registered.

After LPM.dev approves a request

LPM.dev renames the organization to the name. The previous slug of an organization redirects to it for 90 days.

Nobody can publish under the name for 72 hours after the approval. During those 72 hours, LPM.dev can undo the approval. An undo renames the organization back, and it releases the owner's tunnel domains that use the name.

LPM.dev emails the owners and the requester. If the LPM GitHub App is installed on the brand's GitHub organization, LPM.dev also emails the organization's admins, at the address of their linked LPM.dev account and at the public email of their GitHub profile. They can object before anything publishes.

A name that published does not move

When an owner publishes its first package, its name is locked. LPM.dev moves a locked name to another owner only for one of these reasons:

  • An account compromise, such as a stolen DNS or GitHub login that was used to get a company's name
  • A court order
  • A malware takedown

When a name moves, LPM.dev pauses publishing under the name, and then it does these things:

  1. LPM.dev quarantines every release that the previous owner published under the name. The releases do not install.
  2. LPM.dev retires every package name that was published under the name. Nobody can publish a retired package name again, so an existing dependency never installs the new owner's code.
  3. The previous owner keeps its account under a new name, and it can publish new packages under that name. LPM.dev releases the previous owner's tunnel domains that use the name.
  4. LPM.dev renames the new owner to the name.

A company or project name on the list moves only to an organization.

LPM.dev emails the owners of both accounts or organizations.

Disputes

If you think that someone uses your company's or your project's name to impersonate you, email support@lpm.dev. Give the name and the evidence that the name is yours, such as your domain or your GitHub organization.

If the name has not published, LPM.dev can add it to the list of protected names. Then you can request it. If the name published, LPM.dev moves it only for one of the reasons above. LPM.dev does not take a name from an owner because the owner is inactive.

Names are not for sale

LPM.dev does not sell names. LPM.dev does not auction names, and it does not charge for a short name.