Governance
How decisions get made
theAuth is maintained by GLINR STUDIOS, a GLINCKER LLC project. Both repositories publish a governance file. No individual maintainers are named; contact is support@glincker.com.
Sources and review date
SourceLast reviewed 2026-10-06
- Source
- theauth-go GOVERNANCE.md and MAINTAINERS.md; theauth GOVERNANCE.md and MAINTAINERS.md.
- Last reviewed
- 2026-10-06. Summaries on this page are written by hand and checked against the linked documents on that date. The documents themselves are the record.
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.
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. 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. 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@glincker.com. The TypeScript repository says maintainers are invited based on sustained, high-quality contributions.
- Contactsupport@glincker.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
Get started
Give your first agent an identity.
Install the package, create an agent with scoped permissions, and read its first audit record. The core runs on Postgres, SQLite, MySQL or D1, and the Go module needs a single go get.
npm install @glinr/theauthgo get github.com/glincker/theauth-go