Skip to content

Commit 546a4b5

Browse files
authored
disputes: update policy to reflect new form (npm#21)
There is a new streamlined form for naming disputes. We are going to direct all traffic this way so it is better to be explicit in the policy rather than sending people to a form to forward them to another form.
1 parent 66a4e86 commit 546a4b5

File tree

1 file changed

+2
-39
lines changed

1 file changed

+2
-39
lines changed

content/policies/disputes.mdx

Lines changed: 2 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,8 @@ of the npm Code of Conduct or Open-Source Terms.
1515

1616
## tl;dr
1717

18-
1. Open a support ticket at <https://npmjs.com/support>
19-
1. Explain why you require a package, org, or username transferred
18+
1. Open a support ticket at <https://support.github.com/contact/npm-name-disputes>.
19+
1. Fill out the form with as much detail as possible.
2020
1. Support will address your request. Please note submitting a report does not
2121
guarantee the transfer of a package, org, or username.
2222

@@ -52,43 +52,6 @@ but giving that name to the requesting party would pose a supply-chain risk
5252
to the npm ecosystem. In such cases, requests may be denied independent of
5353
the validity of the claim.
5454

55-
## Beginning the process
56-
57-
### Packages
58-
59-
To dispute a package called `foo`, follow these steps:
60-
61-
1. Open a support ticket at <https://npmjs.com/support>, indicating that
62-
you would like to start the process to request ownership of the `foo`
63-
package. Please explain the why you believe the package should be transferred.
64-
You will get an automated reply from npm support to your email address.
65-
1. Support will address your request. Please note submitting a report does not
66-
guarantee the transfer of a package.
67-
68-
### Organizations
69-
70-
To dispute an organization name, follow these steps:
71-
72-
1. Open a support ticket at <https://npmjs.com/support>, indicating that
73-
you dispute an organization name. Include the name of the organization,
74-
e.g. `@foo`. Please explain the why you believe the Organizations should
75-
be transferred. You will get an automated reply from npm support to your
76-
email address.
77-
1. Support will address your request. Please note submitting a report does not
78-
guarantee the transfer of an organization.
79-
80-
### User names
81-
82-
To dispute a user name, follow these steps:
83-
84-
1. Open a support ticket at <https://npmjs.com/support>, indicating that
85-
you dispute a user name. Include the name of the user account,
86-
e.g. `@foo`. Please explain why you believe the Username should be
87-
transferred. You will get an automated reply from npm support to your
88-
email address.
89-
1. Support will address your request. Please note submitting a report does not
90-
guarantee the transfer of a user name.
91-
9255
## Trademarks
9356

9457
npm processes Trademark claims under GitHub's [Trademark Policy](https://docs.github.com/site-policy/content-removal-policies/github-trademark-policy).

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy