@@ -25,6 +25,12 @@ them. If necessary, the team may reach out to inactive maintainers and help
25
25
mediate the process of ownership transfer.
26
26
</p >
27
27
28
+ <p >
29
+ Using an automated tool to claim ownership of a large number of package names
30
+ is not permitted. We reserve the right to block traffic or revoke ownership
31
+ of any package we determine to have been claimed by an automated tool.
32
+ </p >
33
+
28
34
<h2 id =' removal' ><a href =' #removal' >Removal</a ></h2 >
29
35
30
36
<p >
@@ -101,46 +107,3 @@ more details.
101
107
<p >
102
108
Thank you for taking the time to responsibly disclose any issues you find.
103
109
</p >
104
-
105
- <h2 id =' crawlers' ><a href =' #crawlers' >Crawlers</a ></h2 >
106
-
107
- <p >
108
- Before resorting to crawling crates.io, you should first see if you are able to
109
- gather the information you need from the <a href =' https://github.com/rust-lang/crates.io-index' >
110
- crates.io index</a >, which is a public git repository containing the majority
111
- of the information availble through our API.
112
-
113
- If the index does not have the information you need, we're also happy to
114
- discuss solutions to your needs that don't require you to crawl the registry.
115
- You can email us at <a href =" mailto:help@crates.io" >help@crates.io</a >.
116
- </p >
117
-
118
- <p >
119
- We allow our API and website to be crawled by commercial crawlers such as
120
- GoogleBot. At our discretion, we may choose to allow access to experimental
121
- crawlers, as long as they limit their request rate to 1 request per second or
122
- less.
123
- </p >
124
-
125
- <p >
126
- We also require all crawlers to provide a user-agent header that allows us to
127
- uniquely identify your bot. This allows us to more accurately monitor any
128
- impact your bot may have on our service. Providing a user agent that only
129
- identifies your HTTP client library (such as "<code >request/0.9.1</code >") increases the
130
- likelihood that we will block your traffic.
131
-
132
- It is recommended, but not required, to include contact information in your user
133
- agent. This allows us to contact you if we would like a change in your bot's
134
- behavior without having to block your traffic.
135
- </p >
136
-
137
- <p >
138
- Bad: "<code >User-Agent: reqwest/0.9.1</code >"<br >
139
- Better: "<code >User-Agent: my_bot</code >"<br >
140
- Best: "<code >User-Agent: my_bot (my_bot.com/info)</code >" or "<code >User-Agent: my_bot (help@my_bot.com)</code >"
141
- </p >
142
-
143
- <p >
144
- We reserve the right to block traffic from any bot that we determine to be in
145
- violation of this policy or causing an impact on the integrity of our service.
146
- </p >
0 commit comments