Consider archiving this repo

[DamareYoh]

This repo is widely popular, but has a 4 month old critical defect #73, and uses tagging practices that incentivize people to unsafely include master in their projects. This is dangerous for the go ecosystem as a whole.

Please archive this repo if there is no intention to maintain it further.

[miguelbemartin]

Hi @DamareYoh, do you know some alternative to this repo?

[DamareYoh]

Hi @miguelbemartin, the Gophers slack community has set up a Github Org, and they're in progress on a semi official community supported fork of this here: https://github.com/gofrs/uuid. The advantage of this one would be it would be a drop in replacement for folks who have already gone through the pain of upgrading 6 months ago.

It's still pending merge of the critical defect fix while they get the repo set up. They are also improving the available tests. But there should be updates shortly.

[kevinburke]

I maintain a fork that doesn't have the critical rand error, and maintains the old API as is. https://github.com/kevinburke/go.uuid

Others would be github.com/pborman/uuid, github.com/google/uuid.

[miguelbemartin]

Thanks, @DamareYoh @kevinburke! As I am working on a pet project, I will keep using a fork also.

[cameracker]

The community maintained UUID package has released: https://github.com/gofrs/uuid/releases/tag/v2.0.0

[kishaningithub]

Google also has a UUID package

https://github.com/google/uuid