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 connect is a slim RPC framework built on Protocol Buffers and net/http. In addition to supporting its own protocol, Connect handlers and clients are wire-compatible with gRPC and gRPC-Web, including streaming.
This package provides a SASL library written in Go.
Gorilla WebSocket is a Go implementation of the WebSocket protocol.
Package ws implements a client and server for the WebSocket protocol as specified in RFC 6455.
The html2text package converts HTML emails to plain text, allowing text-only mail clients to display them.
This package is intended to be used by bridges between existing logging libraries and OpenTelemetry. Users should not directly use this package as a logging library. Instead, install one of the bridges listed in the [registry], and use the associated logging library.
This package provides a Golang implementation of the Javascript Object Signing and Encryption set of standards. This includes support for JSON Web Encryption, JSON Web Signature, and JSON Web Token standards.
Package smithy provides the core components for a Smithy SDK.
This package provides a CSS3 tokenizer.
Package proton implements types for accessing the Proton API.
This package implements a TCP-level socket options that allow manipulation of TCP connection facilities.
Package packet provides access to Linux packet sockets (https://www.man7.org/linux/man-pages/man7/packet.7.html).
If you use certificate-based access to protect your Google Cloud resources, the end user device certificate is one of the credentials that is verified before access to a resource is granted. You can configure Google Cloud to use the device certificates in your operating system key store when verifying access to a resource from the gcloud CLI or Terraform by using the enterprise certificates feature.
Package s3 provides the API client, operations, and parameter types for Amazon Simple Storage Service.
This package provides an interface for implementing milter mail filters for Go.
Package gohttpmetrics knows how to measure http metrics in different metric formats, it comes with a middleware that can be used for different frameworks and also the the main Go net/http handler:.
wazero is a WebAssembly Core Specification 1.0 and https://www.w3.org/TR/2022/WD-wasm-core-2-20220419/,2.0 compliant runtime. It has zero dependencies, and doesn't rely on CGO. This means you can run applications in other languages and still keep cross compilation.
This package provides implementations of various JWx (JWA/JWE/JWK/JWS/JWT, otherwise known as JOSE) technologies.
Package ttrpc defines and implements a low level simple transfer protocol optimized for low latency and reliable connections between processes on the same host. The protocol uses simple framing for sending requests, responses, and data using multiple streams.
Gorilla/Mux implements a request router and dispatcher for matching incoming requests with their respective handler.
Package putio is the Put.io API v2 client for Go. It's an alternative fork of https://github.com/igungor/go-putio.
This is a Go port of the exponential backoff algorithm from Google's HTTP Client Library for Java.
Exponential backoff is an algorithm that uses feedback to multiplicatively decrease the rate of some process, in order to gradually find an acceptable rate. The retries exponentially increase and stop increasing when a certain threshold is met.
certmagic provides API for TLS Automation with full control over almost every aspect of the system.
Main features:
Fully automated certificate management including issuance and renewal, with support for certificate revocation. Also works in conjunction with your own certificates.
Wildcard certificates.
One-line, fully managed HTTPS servers, with HTTP->HTTPS redirects.
Multiple issuers supported: get certificates from multiple sources/CAs for redundancy and resiliency.
Solves all 3 common ACME challenges: HTTP, TLS-ALPN, and DNS (and capable of others.)
Robust error handling:
Challenges are randomized to avoid accidental dependence and rotated to overcome certain network blockages.
Robust retries for up to 30 days.
Exponential backoff with carefully-tuned intervals.
Retries with optional test/staging CA endpoint instead of production, to avoid rate limits.
All libdns DNS providers work out-of-the-box.
Pluggable storage backends (default: file system) and key sources.
Automatic OCSP stapling.
Distributed solving of all challenges (works behind load balancers.)
Supports on-demand issuance of certificates.
Optional event hooks for observation.
One-time private keys by default (new key for each cert) to discourage pinning and reduce scope of key compromise.
Works with any certificate authority (CA) compliant with the ACME specification RFC 8555.
Must-Staple (optional; not default.)
Full support for draft-ietf-acme-ari (ACME Renewal Information; ARI) extension.
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.