OpenMaintainer

AI-native workbench for open-source maintainers.

stable

Demo modeDeterministic fallback

First maintainer session

Run one calm maintenance loop before touching GitHub.

Inspect repository

Enter demo or owner/repo. No credentials required.

Pick today's focus

Open Focus and choose one blocker that reduces waiting or release risk.

Copy a human-approved handoff

Use Contributors or Review to copy a reply, PR handoff, or GitHub CLI draft.

Focus plan

3 focus blocks can reduce release risk and contributor waiting today

minutes today

criticalrelease · 20m

Resolve high-priority bug #284

Release gate is blocked by this item

Release blocker is removed or converted into a tracked follow-up

highsla · 10m

PR #92: Refactor GitHub adapter error handling

adapter-owner is 3d over the response target

Contributor receives a clear maintainer response or next step

highreview · 25m

Review risky PR #92

Review focus: error handling, adapter boundaries, regression surface

PR has a focused review path and validation checklist

Decision log

7 maintainer decisions logged: 5 ready, 1 needs review, 1 blocked

ready

review

blocked

Triage issue #284readymediumrespond

Maintainer approves suggested labels and reply before running commands

Priority: highTarget: issue3 maintainer steps

GitHub handoff

3 commands

gh issue edit 284 --repo openmaintainer/demo-repo --add-label "bug" --add-label "priority/high"

Triage issue #287readymediumrespond

Maintainer approves suggested labels and reply before running commands

Priority: highTarget: issue2 maintainer steps

GitHub handoff

3 commands

gh issue edit 287 --repo openmaintainer/demo-repo --add-label "bug" --add-label "priority/high"

Follow up issue #285readylowrespond

Maintainer approves suggested labels and reply before running commands

Priority: normalTarget: issue2 maintainer steps

GitHub handoff

2 commands

gh issue comment 285 --repo openmaintainer/demo-repo --body "Thanks for the proposal. Are you still interested in sending a focused PR for this? If yes, please keep the first change small so it is easy to review."

Follow up issue #286readylowrespond

Maintainer approves suggested labels and reply before running commands

Priority: normalTarget: issue2 maintainer steps

GitHub handoff

2 commands

gh issue comment 286 --repo openmaintainer/demo-repo --body "Thanks for the question. Is this still blocking you, or did the deterministic fallback answer your workshop use case?"

Review PR #92readylowreview

Maintainer reviews suggested focus and validation before posting

Priority: normalTarget: pull-request2 maintainer steps

GitHub handoff

2 commands

gh pr view 92 --repo openmaintainer/demo-repo --web

Review duplicate issues #284/#287needs-reviewhighclose

Human review required before close or release command

Priority: normalTarget: issue3 maintainer steps

GitHub handoff

3 commands

gh issue comment 287 --repo openmaintainer/demo-repo --body "This looks related to #284. I am going to keep #284 as the canonical thread so reproduction details stay in one place."

Prepare release draftblockedhighrelease

Release gate is blocked; do not run release command yet

Priority: normalTarget: release2 maintainer steps

GitHub handoff

1 command

gh release create --repo openmaintainer/demo-repo --draft --notes-file RELEASE_NOTES.md

Ownership routing

7 ownership routes assigned across 4 maintainer roles

Release captain

Triage maintainer

Review maintainer

Safety reviewer

Release captain

criticalrelease

Resolve high-priority bug #284

Release gate is blocked by this item

Thanks for reporting this. Could you share the exact command output, runtime version, OS version, and a minimal reproduction so we can verify the failure path?

Release captain

criticalrelease

Collect reproduction details for #284

Release gate is blocked by this item

Missing: Exact command output, Runtime and OS version, Minimal reproduction steps

Safety reviewer

criticaldecision

Prepare release draft

Release gate is blocked; do not run release command yet

Review before running: gh release create --repo openmaintainer/demo-repo --draft --notes-file RELEASE_NOTES.md

Safety reviewer

highdecision

Review duplicate issues #284/#287

Human review required before close or release command

Review before running: gh issue comment 287 --repo openmaintainer/demo-repo --body "This looks related to #284. I am going to keep #284 as the canonical thread so reproduction details stay in one place."

Triage maintainer

highsla

Issue #285: Add Chinese README quickstart

cn-maintainer is 3d over the response target

Ask whether the contributor still wants to send a focused PR

Triage maintainer

highsla

PR #92: Refactor GitHub adapter error handling

adapter-owner is 3d over the response target

Review PR #92

Review maintainer

highreview

Review risky PR #92

Review focus: error handling, adapter boundaries, regression surface

Thanks for the PR. I am going to focus review on error handling, adapter boundaries, and regression surface. Suggested validation before merge: Run existing unit tests before merge; Add regression coverage for changed edge cases.

Public status

Release is blocked; 6 contributor threads need maintainer attention; 2 starter tasks are open

Release status

Release blocked by 4 blockers and 2 warnings

release · 20msla · 10mreview · 25m

Waiting on maintainer

workshop-hostoverdue

Issue #286: Question: can the triage model run without an API key?

windows-useroverdue

Issue #287: Install script fails on Windows when pnpm is missing

adapter-owneroverdue

PR #92: Refactor GitHub adapter error handling

Contributors can help

starterstarter/issue-285-chinese-readme-quickstart

Issue #285: Add Chinese README quickstart

guidedstarter/issue-286-question-can-the-triage-model-run-without-an-api

Issue #286: Question: can the triage model run without an API key?

Reply outbox

5 contributor replies are ready to send

ready replies

urgent

Issue #284: Windows install fails when pnpm is not already availableurgentrepro · issue #284English / 中文

first-time-contributor

English

Thanks for reporting this. To help us reproduce it quickly, could you add exact command output, runtime and OS version, and minimal reproduction steps? Once those details are in the issue, a maintainer can verify the failure path.

中文

感谢反馈。为了帮助我们快速复现，请补充完整命令输出、运行时和 OS 版本和最小复现步骤。信息补齐后，维护者就可以验证失败路径并继续推进。

GitHub handoff

gh issue comment 284 --repo openmaintainer/demo-repo --body 'Thanks for reporting this. To help us reproduce it quickly, could you add exact command output, runtime and OS version, and minimal reproduction steps? Once those details are in the issue, a maintainer can verify the failure path.'

Issue #287: Install script fails on Windows when pnpm is missingurgentrepro · issue #287English / 中文

windows-user

English

中文

感谢反馈。为了帮助我们快速复现，请补充完整命令输出、运行时和 OS 版本和最小复现步骤。信息补齐后，维护者就可以验证失败路径并继续推进。

GitHub handoff

gh issue comment 287 --repo openmaintainer/demo-repo --body 'Thanks for reporting this. To help us reproduce it quickly, could you add exact command output, runtime and OS version, and minimal reproduction steps? Once those details are in the issue, a maintainer can verify the failure path.'

PR #92: Refactor GitHub adapter error handlinghighreview · PR #92English / 中文

adapter-owner

English

中文

感谢提交 PR。我会重点检查 error handling、adapter boundaries、regression surface。合并前建议验证：Run existing unit tests before merge；Add regression coverage for changed edge cases。

GitHub handoff

gh pr comment 92 --repo openmaintainer/demo-repo --body 'Thanks for the PR. I am going to focus review on error handling, adapter boundaries, and regression surface. Suggested validation before merge: Run existing unit tests before merge; Add regression coverage for changed edge cases.'

Issue #285: Add Chinese README quickstartnormalstarter · issue #285English / 中文

cn-maintainer

English

This is a good starter task. Suggested scope: Add a focused documentation change for the requested quickstart. Please open a small PR from starter/issue-285-chinese-readme-quickstart, link back to issue #285, and use the checklist in the PR body.

中文

这是一个适合开始贡献的任务。建议范围：Add a focused documentation change for the requested quickstart。请从 starter/issue-285-chinese-readme-quickstart 开一个小 PR，关联 issue #285，并在 PR body 里使用 checklist。

GitHub handoff

gh issue comment 285 --repo openmaintainer/demo-repo --body 'This is a good starter task. Suggested scope: Add a focused documentation change for the requested quickstart. Please open a small PR from starter/issue-285-chinese-readme-quickstart, link back to issue #285, and use the checklist in the PR body.'

Maintainer inbox

2 repositories, 86 open issues, 3 open pull requests

Most painful

openmaintainer/urgent-sdk

Repositories

Open issues

Open PRs

Critical repos

openmaintainer/urgent-sdkcritical · 100

82 open issues
Missing license
Oldest pull request is 14 days old
Issue response gap: Oldest open issue was updated 9 days ago

Next action

Triage issue #284

openmaintainer/docs-kitcalm · 15

Queue is currently manageable

Next action

Prepare release draft

OSS evidence pack

Prepared for Codex for Open Source review: maintenance load, contributor impact, and human-approved automation use.

Why this repository qualifies

openmaintainer/demo-repo has 1,284 GitHub stars, 37 open issues, and active contributor traffic. OpenMaintainer shows concrete maintenance load: 6 contributor-facing blockers across 6 contributors, duplicate cleanup, stale follow-ups, PR review focus, and release preparation.

API credit usage

API credits will power maintainer automation: issue triage, contributor unblock queues, duplicate detection, pull request review focus, release notes, and evidence packs. All actions remain human-approved before touching GitHub.

Evidence

37 open issues and 2 open pull requests need maintainer attention
6 contributor-facing blockers across 6 contributors
7 maintainer actions are ready for human-approved execution
2 high-priority issue responses, 1 PR review workflows, and 1 release workflow
OSS readiness 90/100 and health 74/100 are tracked with repeatable checks

Codex for Open Source

Application packet

Form-ready answers for the official Codex for Open Source application.

GitHub repository URL

https://github.com/openmaintainer/demo-repo

Describe your role

Core maintainer

Why does this repository qualify?

I'm interested in...

Codex Security; API credits for my project

How will you use API credits for your project?

Anything else we should know?

This project is built specifically around real OSS maintenance workflows: reducing contributor waiting time, surfacing the most painful queues first, and turning Codex output into reviewable maintainer actions instead of opaque automation.

Starter kit

2 starter tasks are ready for new contributors

Issue #285: Add Chinese README quickstartstarter

starter/issue-285-chinese-readme-quickstart

Acceptance

Add a focused documentation change for the requested quickstart
Keep the change small enough for a first review
Include before/after context in the pull request body

Issue #286: Question: can the triage model run without an API key?guided

This is a good starter task. Suggested scope: Add a short answer or example that resolves the question. Please open a small PR from starter/issue-286-question-can-the-triage-model-run-without-an-api, link back to issue #286, and use the checklist in the PR body.

starter/issue-286-question-can-the-triage-model-run-without-an-api

Acceptance

Add a short answer or example that resolves the question
Keep the change focused on one documented workflow
Include before/after context in the pull request body

Response SLA

6 contributor threads need attention: 6 overdue, 0 at risk

overdue

at risk

on track

PR #92: Refactor GitHub adapter error handlingoverdue

adapter-owner waited 5d; target is 2d.

Review PR #92

Issue #285: Add Chinese README quickstartoverdue

cn-maintainer waited 4d; target is 1d.

Ask whether the contributor still wants to send a focused PR

Issue #286: Question: can the triage model run without an API key?overdue

workshop-host waited 4d; target is 1d.

Ask whether the question is still blocking the contributor

Issue #284: Windows install fails when pnpm is not already availableoverdue

first-time-contributor waited 4d; target is 1d.

Triage issue #284

Repro kit

2 bug reports need reproducible details before maintainers can act

Issue #284: Windows install fails when pnpm is not already available3 missing

Checklist

Exact command output
Runtime and OS version
Minimal reproduction steps

Issue #287: Install script fails on Windows when pnpm is missing3 missing

Checklist

Exact command output
Runtime and OS version
Minimal reproduction steps

Contributor impact

6 contributor-facing blockers across 6 contributors

contributors

blocked

avg wait

Unblock kit

4 blocked contributors can be unblocked with 9 maintainer commands

cn-maintainer

Issue #285: Add Chinese README quickstart

2 commands

workshop-host

Issue #286: Question: can the triage model run without an API key?

2 commands

adapter-owner

PR #92: Refactor GitHub adapter error handling

2 commands

first-time-contributor

Issue #284: Windows install fails when pnpm is not already available

3 commands

Ready to paste

Includes maintainer replies and GitHub CLI commands for blocked contributors.

Issue #285: Add Chinese README quickstartblocked · 4d

cn-maintainer is waiting for maintainer movement.

Unblock

Ask whether the contributor still wants to send a focused PR

Issue #286: Question: can the triage model run without an API key?blocked · 4d

workshop-host is waiting for maintainer movement.

Unblock

Ask whether the question is still blocking the contributor

PR #92: Refactor GitHub adapter error handlingblocked · 5d

adapter-owner is waiting for maintainer movement.

Unblock

Review PR #92

Issue #284: Windows install fails when pnpm is not already availableblocked · 4d

first-time-contributor is waiting for maintainer movement.

Unblock

Triage issue #284

Repository

openmaintainer/demo-repo

A demo repository used to show how OpenMaintainer helps maintainers triage issues and review pull requests.

GitHub

1,284

Stars

Open issues

Pull requests

74/100

Health

90/100

Readiness

Strengths

MIT license is discoverable
Active pull requests create a clear maintenance queue

Risks

2 high-priority issue needs maintainer review
Open issue queue may become hard to scan manually

Next actions

Review high-priority triage items first
Ask for missing reproduction details before debugging
Keep release notes updated from active pull requests

Command queue

16 GitHub commands across 7 maintainer actions are staged for human-approved execution

Triage issue #284high

3 commands

reviewWrites labels or comments

Ready

Triage issue #287high

3 commands

reviewWrites labels or comments

Ready

Follow up issue #285normal

2 commands

reviewWrites labels or comments

Ready

Follow up issue #286normal

2 commands

reviewWrites labels or comments

Ready

Human approval gate

Commands are staged for maintainer review. Close and release commands are flagged before running.

Command safety

Safe

Review

Destructive

Safe: Read-only GitHub command

Review: Writes labels or comments

Destructive: Contains close, delete, or release command

2 review gates

PR handoff

1 pull request needs focused review handoff before contributors wait longer

PR #92: Refactor GitHub adapter error handlingmedium

error handlingadapter boundariesregression surface

Validation

Run existing unit tests before merge
Add regression coverage for changed edge cases

OSS readiness

90/100

pass

License

MIT is visible to contributors

pass

Repository description

Description explains the project purpose

pass

Default branch

Default branch is main

warn

Issue load

Open issue count is high enough to need active triage

pass

Review queue

Pull request queue is reviewable

Quality signals

4 signals

Label coverage

2 of 4 open issues already have labels

2 unlabeled open issues
50% issue label coverage
Target label coverage 100%
Preferred labels bug, documentation, question, feature, needs-triage

Label unlabeled issues before deeper triage work

Issue response gap

Oldest open issue was updated 2 days ago

Oldest issue updated 2 days ago
Target response gap 1 days

Refresh older issue threads with a maintainer response

Pull request age

Oldest open pull request is 3 days old

2 open pull requests
Target PR age 2 days

Assign review ownership for aging pull requests

Review load

2 open pull requests in the review queue

100

Review load score 100/100
Target open PRs 8

Review queue is small enough for focused maintainer attention

Maintenance queue

4 items

#284 Windows install fails when pnpm is not already availablehigh

Thanks for reporting this. Could you share the exact command output, runtime version, OS version, and a minimal reproduction so we can verify the failure path?

Labels

bugpriority/highgood-first-response

#285 Add Chinese README quickstartlow

Thanks for opening this. This looks useful; a small focused PR with docs and tests would make it easier to review.

Labels

documentationneeds-triage

#286 Question: can the triage model run without an API key?normal

Thanks for the question. This should work in demo mode without credentials; maintainers can add API keys later for stronger AI summaries.

Labels

questionneeds-triage

#287 Install script fails on Windows when pnpm is missinghigh

Thanks for reporting this. Could you share the exact command output, runtime version, OS version, and a minimal reproduction so we can verify the failure path?

Labels

bugpriority/high

Similar issues

1 clusters

#284#287

Shared maintainer context: windows, install, fails, pnpm

Review together before asking contributors for duplicate reproduction details

Maintainer settings

5 labels

Target label coverageMax issue response daysMax PR age daysMax open PRsRelease cadence days

Preferred labels

Trend memory

improving

Health +6, readiness +10, open issues -5, open PRs -2 since 2026-05-25

Health score

68 -> 74

Readiness score

+10

80 -> 90

Open issues

-5

42 -> 37

Open PRs

-2

4 -> 2

Quality movement

Label coverage+25

Issue response gap+10

Pull request age+37

Review load+32

Weekly digest

watch

Weekly maintainer digest for openmaintainer/demo-repo

Release readiness: ready-with-review

Highlights

Health score 74/100 with stable status
OSS readiness 90/100
2 high-priority maintainer actions
1 similar issue clusters detected
30-day release cadence target

Defer

Lower-risk queue
Duplicate cleanup

Priorities

Triage issue #284: Windows install fails when pnpm is not already available
Triage issue #287: Install script fails on Windows when pnpm is missing
Review PR #92: Refactor GitHub adapter error handling changes 6 files with 214 additions and 87 deletions.

Repository playbooks

Today

Stabilize the highest-risk maintainer queue first.

daily

1
Triage #284
high high-priority issue needs a maintainer response before deeper debugging.
Contributor receives a clear next step and the issue gains actionable labels.
2
Triage #287
high high-priority issue needs a maintainer response before deeper debugging.
Contributor receives a clear next step and the issue gains actionable labels.
3
Follow up issue #285
normal high-priority issue needs a maintainer response before deeper debugging.
Contributor receives a clear next step and the issue gains actionable labels.

This week

Reduce review uncertainty before the pull request queue grows stale.

weekly

1
Review PR #92
Review-risk action should be checked while repository context is fresh.
Maintainer has a focused review path and test checklist.

Before release

Turn current maintenance work into a publishable release draft within a 30-day cadence.

release

1
Prepare release draft
Release notes should be prepared from active pull requests before publish pressure rises.
Draft release notes are ready for human review.

Action plan

Triage issue #284high

Windows install fails when pnpm is not already available

Apply labels: bug, priority/high
Consider contributor label: good-first-response
Request missing information: Exact command output, Runtime and OS version, Minimal reproduction steps

GitHub handoff

gh issue edit 284 --repo openmaintainer/demo-repo --add-label "bug" --add-label "priority/high"
gh issue comment 284 --repo openmaintainer/demo-repo --body "Thanks for reporting this. Could you share the exact command output, runtime version, OS version, and a minimal reproduction so we can verify the failure path?"
gh issue view 284 --repo openmaintainer/demo-repo --web

Triage issue #287high

Install script fails on Windows when pnpm is missing

Apply labels: bug, priority/high
Request missing information: Exact command output, Runtime and OS version, Minimal reproduction steps

GitHub handoff

gh issue edit 287 --repo openmaintainer/demo-repo --add-label "bug" --add-label "priority/high"
gh issue comment 287 --repo openmaintainer/demo-repo --body "Thanks for reporting this. Could you share the exact command output, runtime version, OS version, and a minimal reproduction so we can verify the failure path?"
gh issue view 287 --repo openmaintainer/demo-repo --web

Follow up issue #285normal

Issue #285 has been quiet for 2 days.

Refresh issue #285 because it has been quiet for 2 days
Ask whether the contributor still wants to send a focused PR

GitHub handoff

gh issue comment 285 --repo openmaintainer/demo-repo --body "Thanks for the proposal. Are you still interested in sending a focused PR for this? If yes, please keep the first change small so it is easy to review."
gh issue view 285 --repo openmaintainer/demo-repo --web

Follow up issue #286normal

Issue #286 has been quiet for 2 days.

Refresh issue #286 because it has been quiet for 2 days
Ask whether the question is still blocking the contributor

GitHub handoff

gh issue comment 286 --repo openmaintainer/demo-repo --body "Thanks for the question. Is this still blocking you, or did the deterministic fallback answer your workshop use case?"
gh issue view 286 --repo openmaintainer/demo-repo --web

Review duplicate issues #284/#287normal

Compare #284 and #287: Shared maintainer context: windows, install, fails, pnpm

Compare issue #284 with #287 before closing either thread
Keep #284 as the canonical issue
Close only after confirming the reports describe the same failure path

GitHub handoff

gh issue comment 287 --repo openmaintainer/demo-repo --body "This looks related to #284. I am going to keep #284 as the canonical thread so reproduction details stay in one place."
gh issue close 287 --repo openmaintainer/demo-repo --reason "not planned"
gh issue view 284 --repo openmaintainer/demo-repo --web

Review PR #92normal

Refactor GitHub adapter error handling changes 6 files with 214 additions and 87 deletions.

Check focus areas: error handling, adapter boundaries, regression surface
Run tests: Run existing unit tests before merge; Add regression coverage for changed edge cases

GitHub handoff

gh pr view 92 --repo openmaintainer/demo-repo --web
gh pr checks 92 --repo openmaintainer/demo-repo

Prepare release draftnormal

Draft release notes from 2 open pull requests.

Copy release draft into GitHub Releases
Verify merged PRs before publishing

GitHub handoff

gh release create --repo openmaintainer/demo-repo --draft --notes-file RELEASE_NOTES.md

Review desk

#92 Refactor GitHub adapter error handlingmedium

Refactor GitHub adapter error handling changes 6 files with 214 additions and 87 deletions.

error handlingadapter boundariesregression surface

#93 Add release notes generatorlow

Add release notes generator changes 3 files with 128 additions and 12 deletions.

release workflow

AI copilot

Maintainer decisions stay human-owned. OpenMaintainer drafts labels, replies, review focus, and release notes for maintainers to approve.

Primary

English OSS

Compatible

中文开发者

Release gate

Release blocked by 4 blockers and 2 warnings

blocked

status

blockers

warnings

Next step

Resolve blockers before publishing a release draft

High-priority bugsfail

2 high-priority bug reports remain open

Reproduction detailsfail

2 bug reports still need reproduction details

Pull request riskwarn

1 pull request review risk needs attention

OSS readinesspass

OSS readiness is 90/100

Release draft

## Release draft for openmaintainer/demo-repo

### Changed
- #92 Refactor GitHub adapter error handling
- #93 Add release notes generator

### Maintainer review focus
- #92: medium risk; check error handling, adapter boundaries, regression surface.
- #93: low risk; check release workflow.