This package implements a functionality to convert Golang's http.Request to CURL command line.

This package provides gorilla/context, which is a general purpose registry for global request variables in the Go programming language.

This package provides a Django-syntax like template-engine.

This package implements OVSDB specified in RFC 7047. It's used mainly for managing the configuration of Open vSwitch and OVN, but it could also be used to manage your stamp collection.

This package providies itegration tests module for k8s.io/kube-openapi.

A simple alternative to rcrowley's go-metrics that's a lot faster (and only does simple bandwidth metrics).

This package implements a functionality which can be used in instrument code, expose application metrics, and profile runtime performance in a flexible manner. It makes use of a MetricSink interface to support delivery to any type of backend.

Currently the following sinks are provided:

• StatsiteSink : Sinks to a statsite instance (TCP)

• StatsdSink: Sinks to a StatsD / statsite instance (UDP)

• PrometheusSink: Sinks to a Prometheus metrics endpoint (exposed via HTTP for scrapes)

• InmemSink : Provides in-memory aggregation, can be used to export stats

• FanoutSink : Sinks to multiple sinks. Enables writing to multiple statsite instances for example

• BlackholeSink : Sinks to nowhere

Package xid is a globally unique id generator suited for web scale. Features:

• zize: 12 bytes (96 bits), smaller than UUID, larger than snowflake

• base32 hex encoded by default (20 chars when transported as printable string, still sortable)

• mon configured, you don't need set a unique machine and/or data center id

• k-ordered

• embedded time with 1 second precision

• unicity guaranteed for 16,777,216 (24 bits) unique ids per second and per host/process

• lock-free (i.e.: unlike UUIDv1 and v2)

The dnsutils package provides a Go function to return a map of Service Records (SRV) in the order they should be used for a given service, protocol and name. The order is determined by the records' priority and randomized selection based on their relative weighting. This package is useful for network applications that require accessing services using SRV records.

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.

This is a parser for GraphQL, written to mirror the graphql-js reference implementation as closely while remaining idiomatic and easy to use.

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.

Package metric provides an implementation of the OpenTelemetry metrics SDK.

This package provides a native DTLS 1.2 implementation in Golang.

This package provides implementations of various JWx (JWA/JWE/JWK/JWS/JWT, otherwise known as JOSE) technologies.

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:.

Package b3 implements the B3 propagator specification as defined at @urlhttps://github.com/openzipkin/b3-propagation,.

Httpsnoop provides an easy way to capture http related metrics (i.e. response time, bytes written, and http status code) from your application's http.Handlers.

ACMEz is a lightweight, fully-compliant RFC 8555 (ACME) implementation, that provides an API for getting certificates. ACMEz is suitable for large-scale enterprise deployments. It also supports common IETF-standardized ACME extensions.

This module has two primary packages:

• acmez is a high-level wrapper for getting certificates. It implements the ACME order flow described in RFC 8555 including challenge solving using pluggable solvers.

• acme is a low-level RFC 8555 implementation that provides the fundamental ACME operations, mainly useful if you have advanced or niche requirements.

Main features:

• Go API that thoroughly documented with spec citations.

• Structured error values (problems as defined in RFC 7807.)

• Smart retries (resilient against network and server hiccups.)

• Challenge plasticity (randomized challenges, and will retry others if one fails.)

• Context cancellation (suitable for high-frequency config changes or reloads.)

• Highly flexible and customizable.

• External Account Binding (EAB) support.

• Tested with numerous ACME CAs (more than just Let's Encrypt.)

• Implements niche aspects of RFC 8555 (such as alt cert chains and account key rollover.)

• Efficient solving of large SAN lists (e.g. for slow DNS record propagation.)

• Utility functions for solving challenges: device attestation challenges (draft-acme-device-attest-02), RFC 8737 (tls-alpn-01 challenge), RFC 8823 (email-reply-00 challenge; S/MIME.)

• ACME Renewal Information (ARI) support (draft-ietf-acme-ari-03.)

Package advancedtls provides gRPC transport credentials that allow easy configuration of advanced TLS features. For example, periodic credential reloading,support for certificate revocation lists, and customizable certificate verification behaviors.

webtransport-go is an implementation of the WebTransport protocol, based on @urlhttps://github.com/quic-go/quic-go,quic-go. It currently implements @urlhttps://www.ietf.org/archive/id/draft-ietf-webtrans-http3-02.html,draft-02 of the specification.

Package vfsgen takes an http.FileSystem (likely at go generate time) and generates Go code that statically implements the provided http.FileSystem.

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

The @codeobfsvpn module contains a Go package that provides server and client components to use variants of the obfs4 obfuscation protocol. It is intended to be used as a drop-in Pluggable Transport for OpenVPN connections (although it can be used for other, more generic purposes).