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.
Package router is a trie based high performance HTTP request router.
Server-sent events is a technology where a browser receives automatic updates from a server via HTTP connection. The SSE EventSource API is standardized as part of HTML5[1] by the W3C.
Package log implements a simple structured logging API designed with few assumptions. Designed for centralized logging solutions such as Kinesis which require encoding and decoding before fanning-out to handlers.
This package is a Go library to talk HTTP over Unix domain sockets.
This package provides a wrapper around the https://openfga.dev/api definition.
OjG is a high performance parser with a variety of additional JSON tools. OjG is optimized to processing huge data sets where data does not necessarily conform to a fixed structure.
Package linkheader provides functions for parsing HTTP Link headers.
This package provides a Go implementation of Coda Hale's Metrics library.
The html2text package converts HTML emails to plain text, allowing text-only mail clients to display them.
This package provides a fully featured interface to the DNS. Both server and client side programming is supported. The package allows complete control over what is sent out to the DNS. The API follows the less-is-more principle, by presenting a small interface.
datadog-go is a library that provides a DogStatsD client in Golang.
WebTunnel is a Go Pluggable Transport that attempts to imitate web browsing activities based on HTTP Upgrade (HTTPT).
The official AWS SDK for the Go programming language.
This package provides basic LDAP v3 functionality in the Go language.
zerossl implements the ZeroSSL REST API.
The REST API is distinct from the ACME endpoint, which is a standardized way of obtaining certificates.
This package provides a plugin system over WebAssembly. As a plugin is compiled to Wasm, it can be size-efficient, memory-safe, sandboxed and portable. The plugin system auto-generates Go SDK for plugins from Protocol Buffers files. While it is powered by Wasm, plugin authors/users don't have to be aware of the Wasm specification since the raw Wasm APIs are capsulated by the SDK.
Package proxyproto implements Proxy Protocol (v1 and v2) parser and writer, as per specification: @urlhttps://www.haproxy.org/download/2.3/doc/proxy-protocol.txt. It is to be used in one of or both proxy clients and proxy servers that need to support said protocol. Both protocol versions, 1 (text-based) and 2 (binary-based) are supported. TLV parsers extensions coming with this library support AWS, Azure and GCP.
Package sdk is the official AWS SDK v2 for the Go programming language.
Package go-nat implements NAT handling facilities.
This package implements a functionality of managing the registration, marshaling, and unmarshaling of encoded types. It helps when types are sent over a ttrpc/GRPC API and marshaled as a protobuf Any.
This package implements a functionality to configure Go's pprof features and default HTTP mux using the environment variable GOPPROF. envpprof has an init function that will run at process initialization that checks the value of the GOPPROF environment variable. The variable can contain a comma-separated list of values, for example GOPPROF=http,block.
Package dap contains data types and code for Debug Adapter Protocol (DAP) specification.
This package contains a client implementation for OAuth 2.0 spec in Go.
This package provides gRPC Go Middlewares: interceptors, helpers and utilities - middleware that is executed either on the gRPC Server before the request is passed onto the user's application logic, or on the gRPC client either around the user call. It is a perfect way to implement common patterns: auth, logging, tracing, metrics, validation, retries, rate limiting and more, which can be a great generic building blocks that make it easy to build multiple microservices easily.