Enter the query into the form above. You can look for specific version of a package by using @ symbol like this: gcc@10.
API method:
GET /api/packages?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel webring send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
This is a linter for Go source code. Unlike gofmt, it doesn't reformat the source code, it only prints out style mistakes.
@codego-vcr simplifies testing by recording your HTTP interactions and replaying them in future runs in order to provide fast, deterministic and accurate testing of your code.
The gls package provides a way to store a retrieve values per-goroutine.
pgmockproxy is a PostgreSQL proxy that logs the messages back and forth between the PostgreSQL client and server. This can aid in building a mocking script by running commands against a real server to observe the results. It can also be used to debug applications that speak the PostgreSQL wire protocol without needing to use a tool like Wireshark.
This package provides tools for detecting deadlocks at run-time in Go.
Package assert implements the same assertions as the assert package but stops test execution when a test fails.
Profile provides a simple way to manage runtime/pprof profiling of your Go application.
This package provides ciinfo, a tool to get details about the current Continuous Integration environment, including checking if running in a CI system, which CI system, build id, and more.
This is a reimplementation of ci-info in Go.
Package quartz is a library for testing time related code. It exports an interface Clock that mimics the standard library time package functions. In production, an implementation that calls thru to the standard library is used. In testing, a Mock clock is used to precisely control and intercept time functions.
Package autogold makes go test -update automatically update Go tests (golden files and Go values in e.g. foo_test.go).
This package provides a test corpus of C code.
This package provides a contract to share variables between test helpers in Golang.
This package provides helpers for automated testing of scanners/lexers/tokenizers.
Package testfs provides a simple fs.FS which is contained in a test (using testing.TB's TempDir) and with a few helper methods.
Ginkgo is a Behaviour-Driven Development testing framework for Go. It builds on top of Go's builtin testing library and is complemented by the Gomega matcher library.
This package is an alternative fork of github.com/icrowley/fake used in go-github-com-jackc-pgx.
Package ogletest provides a framework for writing expressive unit tests. It integrates with the builtin testing package, so it works with the gotest command. Unlike the testing package which offers only basic capabilities for signalling failures, it offers ways to express expectations and get nice failure messages automatically.
This package implements a functionality to scan and report for dependencies which are checked in to the repository. It provides a library and CLI tool.
This package is a simple tracing application that logs messages depending on environment variables. It is very much inspired by git's GIT_TRACE mechanism.
This package provides basic assertions along with building blocks for custom assertions to be used alongside native Go testing.
Staticcheck is a state of the art linter for the Go programming language. Using static analysis, it finds bugs and performance issues, offers simplifications, and enforces style rules.
Package gostub is used for stubbing variables in tests, and resetting the original value once the test has been run.
Package clock provides an abstraction for system time that enables testing of time-sensitive code.
This package implements an extension of Table-Driven Testing. Instead of building and iterating over a table in the test code, the input is further separated into files (or inline strings). For certain classes of tests, this can significantly reduce the friction involved in writing and reading these tests.