Our take
Quietno commits in the last 90 days- Activity
- 31
- Community
- 35
- Issues
- 21
- Pull requests
- 20
+1 stars in the last 30 days
Jorani covers practical leave and overtime workflows, but its quiet recent development and highly concentrated contributions call for checking fit and support expectations before adoption.
Good fit if
- Your organization wants a self-hosted system for leave, overtime, calendars, and balances.
- A single-validator approval flow matches your process.
- You can operate a PHP and MySQL application, or use its Docker Compose setup, and value the MIT license.
Look elsewhere if
- Your approval process requires multiple validators, based on the workflows documented here.
- You need evidence of active recent code changes or broadly distributed project ownership. There have been no commits in the last 90 days, and most code contributions come from one person.
- Your team requires documented CI or automated tests; neither is indicated in the available project data.
All health signals
| Last commit | 2026-04-04 (6 months ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 1 (latest v1.0.4, 2026-03-29) |
| Contributors | 18 (top contributor: 91% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 0 |
| Project age | 12 years |
Checked on 2026-10-13 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
412Forks
283Change since Nov 16, 2026: 0 stars·0 forks
Overview
Jorani is a self-hosted leave and overtime management system for organizations that need employees to submit requests and supervisors to review them. It brings request workflows, leave balances, and attendance information together rather than relying on separate calendars and spreadsheets.
It is aimed at small organizations, with features for departments, organizational structure, and employee calendars. The documented approval workflows use one validator per request.
Key Features
- Leave and overtime request workflows with one validator.
- Leave balance reports filterable by department.
- Monthly presence reports and spreadsheet exports.
- Individual, team, and collaborator leave calendars.
- Organizational tree with employees and supervisors assigned to entities.
- Non-working days configured on contracts or imported.
- OAuth2 REST API, with PHP client examples.
- SSO options including SAML, OpenLDAP, and Active Directory.
Use Cases
- HR teams at small organizations can route employee leave requests to a designated validator.
- Supervisors can review overtime requests and use monthly presence reports to support planning.
- Department managers can check leave balances and team calendars when coordinating coverage.
- Organizations with an existing identity provider can use the documented SSO options, subject to their setup requirements.
What you need
Detected in the repository
- PHP (main language on GitHub)
- A Dockerfile, so it can run in a container; a Compose file sets up the related services
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
The README recommends configuring environment variables in .env, then starting the application with Docker Compose:
docker compose up
See the README for setup details and manual installation instructions.
Alternatives
- horilla-hr: Horilla is a broader HRMS covering records, hiring, attendance, payroll, and performance, while Jorani focuses on leave and overtime workflows.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| jorani | PHP | MIT | 411 | Quiet |
| horilla-hr | HTML | LGPL-2.1 | 1.4k | Active |
Considerations
- The README specifies PHP 8.1+ and MySQL 8+ for the application. Manual installation also requires a database configured with the listed permissions, including
EXECUTEfor MySQL functions. - Project health is marked Quiet: there have been no commits in the last 90 days and no issues closed or pull requests merged in that period. A release was published within the last year, but contributions are concentrated, with one contributor responsible for most of the code.
- The repository data indicates no CI or tests. Teams should assess how they will validate changes and updates.
- The documented workflows specify one validator, which may not suit organizations with more involved approval chains.
- The project uses the MIT license. Review its terms for your deployment and distribution needs.
Found this useful?
Share it with someone who would like jorani.