Skip to content

Latest commit

 

History

History
810 lines (507 loc) · 49.9 KB

CONTRIBUTORS.md

File metadata and controls

810 lines (507 loc) · 49.9 KB

Contributors

Every change in this repository lands with its tests in the same pull request, under a hard 100% line-coverage gate and every check main requires. That is an unusual bar for a project this size, and it means a merged pull request here is evidence about the person who wrote it, not only about the project.

So this is not a thank-you wall. Each entry links to the change itself, so a reader who does not know us can check the claim. If your name is here, the link is yours to use — a CV, a profile README, anywhere the question "what have you actually shipped" comes up.

Nothing here is counted. Not merged pull requests, not changed lines, not closed issues. A count sees how often somebody showed up and misses everything that matters about it: the care taken, the bug nobody else found, the answer written out for a stranger. So the rungs below are judgements rather than totals, and where one is not obvious the reason is written beside the name — CONTRIBUTING.md says what each rung means.

Everyone whose work is in main is here, maintainers included. Bots and coding agents are not — dependabot, Copilot and claude all appear in the repository's commit history and none of them is a person, so listing them beside people would blur the only thing this page is for. git shortlog -sn shows the whole history including theirs. Accounts the organisation has blocked are not listed either.

Within each rung, people are in the order they first landed a change.

Every entry ends with a link to all of that person's merged pull requests, so it is never out of date. Where someone has landed more than two changes, the links above it are a sample.

Maintainer

The people who carry the project: the releases, the review, and the decisions nobody else can make. Their work is most of the history and is not itemised here; the links are a sample.

@cevheri

Organisation member. Wrote most of what is here.

@yusuf-gundogdu

Organisation member. The agent model record, and the distribution inventory.

@kaya-abdullah

Organisation member. The wire-compatible engines, and the first localized READMEs.

Trusted contributor

@harish18092002

The first person outside the core team to send anything at all, on 2025-12-25, when there was no contributing guide, no labeled issue and no reason to believe anyone would answer. Being first is a different act from being second.

@omerfarukbolat

The light theme rests on the shared token layer he built, and the export path escapes every field because of the pass he did over it. Both were the kind of change that moves the floor under everything else rather than fixing one thing.

@suleymansurucu

Came the same day as the first, hours behind it, into the same empty repository. Two people decided this was worth their evening before there was anything here to promise them it would be.

@hbasria

Brought a fifth identity provider into the OIDC layer, and the branch he added is still what runs — src/lib/oidc.ts handles Zitadel's RP-initiated logout because of him. He arrived with the doc and the test in the same change, months before this repository wrote that down as a rule.

@ugurpektas

Built out the admin section: the routes, the interactive UI around them, and the tests that hold it. He did it in one careful pass rather than leaving it half-finished for someone else.

@koraysrn

First into the agent layer, which nobody outside the core team had opened, and he has stayed in it since: its drive ownership, its PostgreSQL grounding and the history of finished runs are all partly his. He started in the part nobody volunteers for, a run behaving correctly when something goes wrong.

@hasnaintypes

Went wherever the work was: the login page, the admin fleet view, a license notice nobody had stated, and the provider docs whose citations had quietly rotted. Each one arrived finished, with the reasoning written down.

Contributor

@ucmazmehmet

@sifaaraldevop

@yangchuansheng

@ducminhle

@wjiec

@Matthew-Selvam

@mfatihdayan

@HasselNot7

@v01dst

@Akimbo92i

@cnYui

@dchaudhari7177

@sonalisrisivani

@be-student

@NormanSMA

@7487

@XiaoZ-0218

@dvd233

@SatvikMishra08

@saad-works

@voidofrgestudio

@SyedMuhamadYasir

@macjayz

@slsgzs-cloud

@stgomoyaa

@mikevillari

@CunjieLee

@nktnet1

@Vetri1706

@TonMtt

@na12334

@Hashir-Ashraf-Awan

@jabrailkhalil

@nightcityblade

@Abdu11ahBilal

@Dharshni-gth

@Swarnabha753

@Dharshini-RS03

@nycjay

@Asgabani

@InnoxCodes

@niukanen1

@costajohnt

@iAmAdheil

@0utsights

@YaoSong808

@Mehmetalpertugtekin

@DevvoLazza

@xiechimon

@Lingikaushikreddy

@Anikesh348

@tunglambk

@nawazish2

@JavierparraDev

@linropx

@sloemo01

@KodYazicam

@t957095

@NotAFlightRisk

@chiliec

@rahimahisah17

@bernalalexis-try

@saitakarcesme

@BladeRunner-KD6-37

@lg114

@Ehtasham-Yasin

@Aditya-XR

@NikharAsthana

@igorwfaoro

@Xavees

@yizhixiaokong

@MohamedIdhries

@TehmeenaAkhtar

@Roberton003

@Reitzzz

@fatihcvs

@MFA-G

@muskanbandta23

@Retsumdk

@shivamcoderrrr

@paulocoutinhox

@Fristail27

@switchcasestudio

@ArthurRamonSouza

@abkucuk

@Maaz2212

@JaredAung

@gurkanceylan41

@rivolity

@berkay-byte

@lb1192176991-lab

@lui01212

@cestercian

@rnihesh

@mgr-punith

@DevKhizerer

@hridhinvarkeyjoseph

@stroexd

@brown-sussy

@Jeevan2410

@abinash2553J

@irfanfaraaz

@SrikanthBonkuri

@itz-puneet

@bizimarda

@jihyunK0617

@siddxwar04

@HannaSalinas

@junaidaliruk

@navpreet-dev

@Furox-Art

@ShahabAhmed01

@Dariusch

@Totopo27

@samusagbt

@CodeByPeace

@notlakshitha

@Vardhan2006

@kkj-buildstr

@Jah-yee

@0x0000x

@sadhana-s-codez

@SwatiManjari

@daemon-tech

@evgessshkin

@Fineturkey

@KrishanKumarAwasthi

@sadfun

@T-Zaid

@yash8233

Getting on this page

Take an issue labelled good first issue — each one states what "done" looks like as a command you can run yourself, so you never have to ask whether you are finished. CONTRIBUTING.md has the setup and the gates.

Reports count too. If you opened an issue that led to a fix, say so on the pull request that fixed it and we will list the report beside the change.