---
title: "theAuth security: practices, disclosure, supply chain"
description: "How theAuth handles hashing, breach checks, rate limiting, signed Go releases and vulnerability disclosure, plus an honest list of what we do not claim."
canonical: https://theauth.dev/security/
lastmod: 2026-10-31
---

Security

# Security practices, stated plainly

What the code does, how releases are signed, and how to report a vulnerability. Grounded in the SECURITY.md files and the Go threat model. No certifications are claimed.

[Read SECURITY.md](https://github.com/glincker/theauth/blob/main/SECURITY.md) [Go threat model](https://docs.theauth.dev/go/security/threat-model)

## Security datasheet

**Datasheet**TypeScript core and Go module

Credentials

Protocol

Supply chain

Hashing differs between the TypeScript and Go libraries because of their runtimes. Pick the one that matches your deployment.

Vulnerability disclosure

## Report privately, never in a public issue

The two repositories publish separate policies. Both prefer GitHub private vulnerability reporting.

- TypeScript repo[Private advisory](https://github.com/glincker/theauth/security/advisories/new) (preferred), or email support@glinr.com with the subject [Security] theauth vulnerability.
- 48 hoursAcknowledgment. Assessment within 5 business days, fix timeline within 10 business days.
- 90 daysPublic disclosure after confirmation, coordinated with the reporter. If a fix cannot ship, we still disclose so users can mitigate.
- Go repo[Private advisory](https://github.com/glincker/theauth-go/security/advisories/new) (preferred), or support@glinr.com. Acknowledgment in 48 hours for critical, high and moderate reports. Fix targets: 14 days critical or high, 30 days moderate. Read the [full Go policy](https://github.com/glincker/theauth-go/blob/main/.github/SECURITY.md).

Full text: [SECURITY.md](https://github.com/glincker/theauth/blob/main/SECURITY.md). Out of scope includes denial of service, social engineering and upstream dependency issues.

## What we do not claim

- **No certifications.** There is no SOC 2, ISO 27001 or ISO 42001 certificate. Compliance material is mapping and evidence, not an attestation.
- **No third-party audit is published** on this site.
- **The operator owns TLS, secrets and infrastructure.** The Go threat model lists these as out of scope.
- **Defaults need tuning.** Go's RequireState is off by default, and revocation propagates to Go resource servers within the introspection cache TTL (60 seconds by default).

- [Agent identity](https://theauth.dev/agent-identity/)
- [Pricing](https://theauth.dev/pricing/)
- [Trust](https://theauth.dev/#trust)
