This package provides an interface for implementing milter mail filters for Go.

This package provides a Go library for authenticating emails.

This package contains a client implementation for OAuth 2.0 spec in Go.

Package rpc2 provides bi-directional RPC client and server similar to net/rpc.

Package ntp provides an implementation of a Simple NTP (SNTP) client capable of querying the current time from a remote NTP server as specified in RFC 5905.

This package provides a validation checker for multiaddrs. Some basic validators for common address types are provided, but creating your own combinations is easy.

This package provides Go code follows the stability guarantees as defined in https://github.com/open-telemetry/opentelemetry-proto?tab=readme-ov-file#maturity-level, maturity level.

Package jsonrpc2 provides a Go implementation of JSON-RPC 2.0.

Package negroni is an idiomatic approach to web middleware in Go. It is tiny,non-intrusive, and encourages use of net/http Handlers.

This package provides SOCKS5 proxy for @urlhttps://github.com/makeworld-the-better-one/go-gemini,go-gemini.

This package provides a re-implementation of Julien Schmidt's httprouter, in that it uses a patricia tree, but the logic is rather different. Specifically, the routing rules are relaxed so that a single path segment may be a wildcard in one route and a static token in another.

Package go-nat implements NAT handling facilities.

Package otlptracegrpc provides an OTLP span exporter using gRPC. By default the telemetry is sent to @urlhttps://localhost:4317.

This package implements RFC 7234 Hypertext Transfer Protocol (HTTP/1.1): Caching.

This package implements RFC 2616 HTTP/1.1 standard.

This package exposes a registry of data types to support string formats in the go-openapi toolkit. strfmt represents a well known string format such as credit card or email. The Go toolkit for OpenAPI specifications knows how to deal with those.

Package jmap implements JMAP Core protocol as defined in RFC 8620 published on July 2019.

bluemonday is a HTML sanitizer implemented in Go.

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.

Package tcpproxy lets users build TCP proxies, optionally making routing decisions based on HTTP/1 Host headers and the SNI hostname in TLS connections.

This package provides helpers to validate Swagger 2.0 specification (aka OpenAPI 2.0).

Web Push API Encryption with VAPID support.

This package implements the IMAP UIDPLUS extension, as defined in @urlhttps://rfc-editor.org/rfc/rfc4315.html, RFC4315.

This package provides a toolkit for building TURN, specified in RFC 8656, servers and clients.

pion/turn is an API for building STUN/TURN clients and servers, not a binary you deploy then configure. It may require copying the examples and making minor modifications to fit your need, no knowledge of Go is required however.

The advantage of this is that you don't need to deal with complicated configuration files, or custom APIs to modify the state of Pion TURN. After you instantiate an instance of a Pion TURN server or client you interact with it like any library. The quickest way to get started is to look at the examples or GoDoc.