PAGES
← all tools
◆ Patch Management

Patchman

open-source

Free plan: not checked yet · Open source: yes

Django-based patch status monitoring tool that tracks package updates available for Linux hosts via a web interface.

What you can do now

Checking Plays…

Summary

Patchman is an open-source patch status monitoring system for Linux that functions via a web interface built on Django. It requires no licensing cost and operates as a service that is populated by running a client on monitored hosts. This tool is intended for systems administrators managing Linux environments, and its documentation positions it alongside similar repository management tools. It maintains active development, having seen 234 commits within the past year from 32 contributors.

Django-based patch status monitoring tool that tracks package updates available for Linux hosts via a web interface.

How Patchman helps

Which hosts have a certain version of a package installed, and which repository it comes from?

The web interface allows filtering to find this information

Which hosts require updates, and are those updates normal or security updates?

The server determines this after clients send package lists and enabled repositories

Which packages are installed that are not from any repository?

The web interface displays information on potential issues like this

What updates are available for each host?

The system determines and displays what updates are available for each host

What patches have been applied to a host?

Plugins like yum, apt, and zypper can send reports to the server every time packages are installed or removed

Which operating system releases and variants are supported?

These can be viewed and filtered through the web interface

Languages

Not documented

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Patchman, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Patchman puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Nothing shipped since we started watching. Releases and docs updates land here as they happen.

last release Nov 4, 2026 · watching since Oct 7, 2026

Project health

Issue, contributor and maintainer activity in furlongm/patchman, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

  1. Contributors not measured distinct committers, last 12 months
  2. Maintainers not measured core set, last 12 months
  3. Bus factor not measured committers behind half the commits
  4. Community-filed 95% of issues opened, last 12 months
  5. Median time to close 56 days first maintainer reply 45 hours
  6. Open backlog 49 of 276 issues ever filed
  1. Issues opened / month 2 · 0 communitymaintainers
  2. Open backlog 49
  3. Contributors / month not measured
  4. Commits / month not measured
  5. Stars not measured
Issue themes, last 12 months
  • bugs 12%
  • features 5%
  • other 83%

Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

Libraries its release ships

What its latest release locks, checked against known advisories.

None of its release's images build from a lockfile we can read.

Add the badge to your README

Maintain this project? The badge links readers straight to this page, so they can follow every release here.

Tracked by Cyber Toolchain Choose a badge style and copy the code →
Saved in this browser. Sign in to sync your tools.