-
Notifications
You must be signed in to change notification settings - Fork 600
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider archiving this repo #83
Comments
Hi @DamareYoh, do you know some alternative to this repo? |
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. |
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. |
Thanks, @DamareYoh @kevinburke! As I am working on a pet project, I will keep using a fork also. |
From satori/go.uuid#83 : satori/go.uuid repo is widely popular, but has a 4 month old critical defect satori/go.uuid#73, and uses tagging practices that incentivize people to unsafely include master in their projects. Remove this project from the awesome list while an alternative emerge from the community.
The community maintained UUID package has released: https://github.com/gofrs/uuid/releases/tag/v2.0.0 |
Google also has a UUID package |
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.
The text was updated successfully, but these errors were encountered: