probot/stale
A GitHub App built with Probot that closes abandoned Issues and Pull Requests after a period of inactivity. observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3460
- days_rel: n/a
- days_push: 1202
- n_releases_24m: 0
Adoption not part of the score
1275 stars · 169 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A Probot-based GitHub App that automatically marks and closes abandoned Issues and Pull Requests after a configurable period of inactivity. It is now deprecated and unmaintained, with users directed to the actions/stale GitHub Action instead.
Use cases
- automatically close stale issues on my github repo
- mark inactive pull requests as stale
- auto-close abandoned issues after 60 days
- github bot to triage inactive issues and PRs
- label and close issues with no recent activity
- reduce backlog of abandoned pull requests
When to choose
- you are already running Probot apps and want issue triage automation
- you need configurable exempt labels, milestones, or assignees for stale detection
When to avoid
- starting a new project - the app is deprecated and unmaintained
- you want ongoing support or updates - use actions/stale instead
Facets
application · maturity abandoned
workflow-automation developer-tools developer-tools version-control cloud github-app probot issue-triage stale-bot deprecated automation web-server nodejs
1 source
- readme: https://github.com/probot/stale · fetched 2026-08-28 · f9150c595b0d
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| probot/stale | main | 10 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem