Ross ROSS = Recommend OSS · open-source software intelligence for agents

go-errors/errors

errors with stacktraces for go observed · 2026-08-28

github.com/go-errors/errors · homepage · Go · MIT (permissive) observed · 2026-08-28

Health v2 · maintenance only

23/100

  • Activity 0
  • Release rhythm 8
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 4241
  • days_rel: n/a
  • days_push: 962
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

1008 stars · 90 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A Go library that adds stacktrace support to errors via an *Error type implementing the standard error interface. It is compatible with stdlib errors.Is/As/Join/Unwrap and was originally created for Bugsnag error reporting.

Use cases

  • capture stack traces when errors occur in go
  • debug unexpected error returns in go applications
  • report errors with stacktraces to bugsnag
  • wrap errors while keeping compatibility with stdlib errors.Is and errors.As
  • print the call stack of an error in go

When to choose

  • you need stacktraces attached to Go errors
  • you want drop-in compatibility with the standard error interface
  • you report errors to services like Bugsnag

When to avoid

  • you only need simple error wrapping without stacktraces (use stdlib fmt.Errorf)
  • you are on Go 1.20+ and only need errors.Join/Unwrap from the standard library

Facets

library · maturity stable

error-handling logging developer-tools developer-tools backend programming-languages go cross-platform stacktrace errors go-library debugging

5 sources

Member repositories

RepositoryRoleHealth v2
go-errors/errorsmain23

For agents

markdown · JSON · MCP: product_card(name="go-errors/errors")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem