Koha

Enterprise-class ILS with modules for acquisitions, circulation, cataloging, label printing, offline circulation for when Internet access is not available, and much more.

Healthy · 71
71/100
Healthy

Actively maintained with regular releases.

Maintenance 37/40
Releases 13/25
Community 5/20
Momentum 15/15

Commit activity more than 93% of tracked projects; popularity more than 26%. How this is calculated.

Commits, last 11 months

2025-12: 113 commits 2026-01: 345 commits 2026-02: 293 commits 2026-03: 494 commits 2026-04: 362 commits 2026-05: 257 commits 2026-06: 219 commits 2026-07: 290 commits 2026-08: 218 commits 2026-09: 442 commits 2026-10: 476 commits
2025-12 3509 total 2026-10
Stars601
Latest release—
Repo updated19 Nov 2026
LicenceGPL-3.0
Built withPerl

Is Koha actively maintained?

Koha is under active development: 3509 commits landed over the last 11 months, averaging roughly 379 commits a month in the most recent quarter.

No tagged releases are published, so there is no stable version to pin to — you would deploy from the default branch or a container image built from it.

Among the 3 document management - integrated library systems (ils) projects we track, Koha currently has the highest health score.

What Koha actually does

Koha is an open-source integrated library system designed to manage library operations such as cataloguing, acquisitions, and circulation. It includes specialised utilities including label printing and an offline circulation mode for operation during internet outages. Built with Perl under the GPL-3.0 licence, it provides a comprehensive suite for document management in institutional settings.

Best fit: It suits public, academic, or special libraries that require a fully featured, self-hosted system to manage physical collections and patron transactions.

Worth knowing: The Perl codebase and extensive feature set can present a significant maintenance and configuration overhead for administrators unfamiliar with the ecosystem.

Deployment notes

As a Perl-based application, it typically requires a dedicated database backend, persistent storage for library data, and a standard reverse proxy setup to handle TLS termination.


Alternatives to Koha

Projects in the same categories, ordered by health score.