auth for agents–from the creator of `dotenv` and `dotenvx`
Rust implementation of IETF RFC 9421, http message signatures
An implementation of RFC 9421, HTTP Message Signatures
NSign (/ˈensaɪn/) is a set of .Net libraries for HTTP Message Signatures (RFC 9421).
A node package for signing and verifying HTTP messages as per RFC 9421 - HTTP Message Signatures specification
An implementation of HTTP Messages Signatures (RFC9421)
Relay and target for Oblivious DoH (ODoH) and ODoH-based Mutualized Oblivious DNS (ODoH-based μODNS; μODoH) supporting (anonymous) authenticated connection, written in Rust.
Authenticate to ICP canisters over HTTP (Proof of Concept)
Example of a A-CUBE webhook server written in Typescript
🔐 Rust bridge: Visa TAP + MCP → AI agents with secure payment auth. RFC 9421 signatures, Ed25519 crypto, JWE encryption. Production-ready, 100% TAP compliant.
Verified-bot identity for AI agents (Web Bot Auth / RFC 9421), with a doctor that reports why a request was blocked.
Lint web-bot-auth key directories - expired keys, wrong curves, http message signature checks etc
Drop-in middleware that detects AI bot traffic. Community-maintained signature database + RFC 9421 Web Bot Auth verification. Node + Python + Go. Apache-2.0.
💡Fork adding support for more signature algorithms.
A vendor-neutral WIMSE (Workload Identity in Multi System Environments) reference implementation in Rust — WIT, WPT, RFC 9421 HTTP signatures, and mTLS/WIC.
The Trust and Mandate Layer for Agentic Commerce — open standard (draft-sam-protocol-01). Merchant-ready. Agent-ready. Bounded autonomy.
Ed25519 + RFC 9421 message signing for A2A agents — reference implementation
RFC9421 HTTP Message Signatures implement for Rust
Add a description, image, and links to the rfc9421 topic page so that developers can more easily learn about it.
To associate your repository with the rfc9421 topic, visit your repo's landing page and select "manage topics."