Install

HmacManager ships as three independently versioned artifacts. They are not alternatives to one another so much as three places the same check can happen.

Artifact	Runs	Install
`HmacManager`	In your ASP.NET Core process	`dotnet add package HmacManager`
Helm chart	In your cluster, as an Istio ext-authz service	`helm install hmac-manager zills/hmac-manager`
`hmac-manager`	In a browser or Node client signing, or a Node service verifying	`npm install hmac-manager`

The .NET library

dotnet add package HmacManager

Targets net8.0 and net10.0. It signs outgoing requests, verifies incoming ones, or both. Continue with the .NET quickstart.

Kubernetes

helm repo add zills https://jzills.github.io/hmac-manager
helm repo update

The chart is also published to GHCR as an OCI artifact:

helm install hmac-manager oci://ghcr.io/jzills/charts/hmac-manager

Container images are on Docker Hub — zills/hmac-manager for the verifier and zills/hmac-manager-operator for the policy controller. Continue with the Kubernetes quickstart.

The JavaScript client

npm install hmac-manager

Signs requests, and verifies them server-side. Ships ESM, CJS and type declarations. Continue with the client quickstart.

The .NET package and the npm package share a version line but not a version number — they are released separately, so the numbers drift. Neither is a lower bound on the other; both speak the same wire format.

.NET quickstart