---
title: "theAuth governance: who maintains it, how it decides"
description: "How GLINCKER, the open-source division of GLINR STUDIOS, maintains theAuth: roles, decisions, releases and how to contact the team."
canonical: https://theauth.dev/open/governance/
lastmod: 2026-10-31
---

Governance

# How decisions get made

theAuth is maintained by GLINCKER, the open-source division of GLINR STUDIOS. Both repositories publish a governance file. No individual maintainers are named; contact is support@glinr.com.

[Go GOVERNANCE.md](https://github.com/glincker/theauth-go/blob/main/GOVERNANCE.md) [TypeScript GOVERNANCE.md](https://github.com/glincker/theauth/blob/main/GOVERNANCE.md)

## Sources and review date

**Source**Last reviewed 2026-10-06

Who

## Maintainers and contributors

Maintainers act for GLINR STUDIOS. Anyone can contribute.

- MaintainersReview and merge pull requests, triage issues and discussions, manage releases, and handle private security reports.
- ContributorsAnyone who opens an issue or discussion, sends a pull request, or improves docs, tests and examples.
- Named peopleNone. Maintainer files describe responsibilities by role.

- Routine changesBug fixes, docs, tests and non-breaking additions are decided in pull request review by a maintainer.
- Larger changesOpen an issue or GitHub Discussion first. State the compatibility impact. A maintainer agrees to the direction, then the pull request is reviewed like any other. New behavior needs tests.
- Breaking changesHandled under the rules on the [stability page](https://theauth.dev/open/stability/).

Decisions

## Small changes fast, big changes discussed

The two repositories describe the same shape of process.

Releases, conduct, joining

## Around the edges

- ReleasesDocumented on the [releases page](https://theauth.dev/open/releases/). The Go governance file says the project does not publish a release schedule.
- Security and conductVulnerabilities are reported privately as described on the [security page](https://theauth.dev/security/). Community behavior follows each repository's code of conduct.
- Becoming a maintainerThe Go repository defines no formal process yet and asks you to say so in a discussion or write to support@glinr.com. The TypeScript repository says maintainers are invited based on sustained, high-quality contributions.
- Contactsupport@glinr.com for anything that does not fit a public channel. Questions and ideas go to GitHub Discussions, and bugs to GitHub issues.

## What we do not claim

- **No foundation or steering committee.** The project is maintained by a company team, as stated.
- **No named maintainers.** Roles and a contact address only.

## Related pages

- [Roadmap](https://theauth.dev/open/roadmap/)
- [Stability](https://theauth.dev/open/stability/)
- [Threat model](https://theauth.dev/open/threat-model/)
- [Releases](https://theauth.dev/open/releases/)
- [Compliance](https://theauth.dev/open/compliance/)
- [Open hub](https://theauth.dev/open/)
- [Security and disclosure](https://theauth.dev/security/)
