Open source
How outside contributions work
Bring bug fixes, bug reports and suggestions. Owners decide new work. This applies wherever our bot maintains a repository, and it is blunt because a clear no costs you less than a slow one. Members, collaborators and dependency bots are not outsiders.
Welcome
Bug fixes
Small and focused, with a test if you can. A small fix goes to review, like any other change.
Bug reports
Steps, what you expected, what happened, the version. If the steps are missing, we ask.
Suggestions
Open an issue and make the case. The owners decide, and a no comes with a reason.
Refused
Dependency changes
Closed. A package added or bumped by a stranger is how a compromise gets in. Updates come from the project’s own bot, and on our projects they wait 14 days.
CI changes
Closed. CI decides what merges and runs with the project’s access. It stays with the owners.
Release changes
Closed. Anything that reaches a published package stays with the people who answer for it.
Agent instruction files
Closed. These files steer the agents working on the repository, so they stay with the owners.
Big rewrites
Closed. A sweeping diff cannot be reviewed well, and the shape of a project is its owners’ call. Fork it if you want a different one.
Unasked features
Declined. A pull request does not decide what a project becomes. Suggest it in an issue first.
Why this strict
Text from outside is data, not instructions
In June 2026 Tenet Security published research it calls Agentjacking: a fake error report, read by a coding agent as if it were guidance, led the agent to run a stranger’s package. Tenet’s results come from controlled testing, and the lesson is ordinary. Our response is equally ordinary: a machine check grades an outside change before a model reads it.
Read Tenet’s write-upWhat is live, as of 2026-11-02
Rolling out: machine grading
An outside pull request in one of the refused classes closes with one technical reason and no model call. Nothing is deleted and your branch stays. A history of merged pull requests earns nothing at the merge step.
Not live yet: bans
Planned as a later part: content judged dangerous closes and bans the account, future items from it close at once, and a ban can apply across developerz.ai accounts. Dependency and rewrite closes never ban.
Live: the bot says it is a bot
When our bot acts as itself it posts as developerz-ai[bot], with GitHub’s Bot badge, and discloses that it is a bot. If you want a person, the appeal below reaches one.
Appeals
Think we got it wrong?
Send us the link through the contact form and say what the close missed. A person on our team replies. A project member who reopens a closed pull request wins, and the bot does not close it again. On a customer’s repository the decision is its owner’s. Bans will use the same route when they ship.
Appeal through the contact formPrivacy
What we read about an account
Today, one thing: the role the account holds on that repository. The content is judged first, without looking at its author. When bans ship, and only after content already looks bad, we will also read the public GitHub profile, and that can only add scrutiny. No reputation score, and no guessing whether a person or an AI wrote it.
Read the privacy policy
Ship more. Maintain less.
We expect software to be written faster than any team can review it. Bring your repos, your boxes and your keys. We bring the org that keeps up.