# Abandoned crates

**URL:** <https://internals.rust-lang.org/t/abandoned-crates/3818>\
**Category:** community\
**Created:** [August 5, 2016, 9:34am UTC](https://internals.rust-lang.org/t/abandoned-crates/3818 "2016-08-05T09:34:27Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![seanmonstar](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/seanmonstar/32/36_2.png) [@seanmonstar](https://internals.rust-lang.org/u/seanmonstar)\
**Post date:** [August 5, 2016, 4:34pm UTC](https://internals.rust-lang.org/t/abandoned-crates/3818/5 "2016-08-05T16:34:17Z")

</div>

> [@dns2utf8](#):
>
> 2.2 Will the code become public domain if the author has not left any mark inside the source?

[crates.io](http://crates.io) requires a license field before you can publish. The code will still be bound by that license, unless the author ever changes said license.

> [@killercup](#):
>
> I think that if you have a good reason (no updates for X months, no answer) and ask @alexcrichton nicely, ownership of a crate (name) can be transferred.

It's not likely to happen. I went through that exact process once, but was deferred to the [Crates.io policy](https://internals.rust-lang.org/t/crates-io-package-policies/1041), which I admittedly had forgotten to look at. The relevant section:

> A more case-by-case policy would be very hard to get right, and would almost certainly result in bad mistakes and and regular controversies.
> 
> Instead, we are going to stick to a first-come, first-served system. If someone wants to take over a package, and the previous owner agrees, the existing maintainer can add them as an owner, and the new maintainer can remove them.

---

_[View the full topic](https://internals.rust-lang.org/t/abandoned-crates/3818)._