Alternative review

violetear alternatives

Packages below are ranked as alternatives in the same category. The trigger for this review is archived repository.

12

Why review alternatives

violetear currently has a maintenance score of 12/100.

Latest repository activity: 3 years ago.

Known Go vulnerability records: 0.

Current package

violetear

Package violetear - HTTP router Basic example: package main import ( "fmt" "github.com/nbari/violetear" "log" "net/http" ) func catchAll(w http.ResponseWriter, r *http.Request) { fmt.Fprintf(w, r.URL.Path[1:]) } func helloWorld(w http.ResponseWriter, r *http.Request) { fmt.Fprintf(w, r.URL.Path[1:]) } func handleUUID(w http.ResponseWriter, r *http.Request) { fmt.Fprintf(w, r.URL.Path[1:]) } func main() { router := violetear.New() router.LogRequests = true router.RequestID = "REQUEST_LOG_ID" router.AddRegex(":uuid", `[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}`) router.HandleFunc("*", catchAll) router.HandleFunc("/hello", helloWorld, "GET,HEAD") router.HandleFunc("/root/:uuid/item", handleUUID, "POST,PUT") srv := &http.Server{ Addr: ":8080", Handler: router, ReadTimeout: 5 * time.Second, WriteTimeout: 7 * time.Second, MaxHeaderBytes: 1 << 20, } log.Fatal(srv.ListenAndServe()) }

Go UUID Libraries 107 stars 87 imported-by 100% confidence
66

Ranked Alternatives

Go UUID Libraries

#1 uuid

Package uuid provides implementations of the Universally Unique Identifier (UUID), as specified in RFC-4122 and the Peabody RFC Draft (revision 03).

Go UUID Libraries 1.8K stars 22.7K imported-by 100% confidence
93

#2 Google UUID

Package uuid generates and inspects UUIDs.

Go UUID Libraries 6.1K stars 113.5K imported-by 100% confidence
78

#3 go.uuid

Package uuid provides implementation of Universally Unique Identifier (UUID).

Go UUID Libraries 4.9K stars 32.8K imported-by 80% confidence
78

#4 ksuid

K-Sortable Globally Unique IDs

Go UUID Libraries 5.3K stars 1.8K imported-by 80% confidence
74

How to use this page

Treat alternatives as a shortlist. Check API compatibility, migration effort, project constraints, and your own threat model before replacing a dependency.