phpro/grumphp

A PHP code-quality tool

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 16th, 2026
Created on March 18th, 2015
Open Issues & Pull Requests: 8 (+0)
GitHub issues: Enabled
Number of forks: 451
Total Stargazers: 4,314 (+0)
Total Subscribers: 69 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.0 hours
Mean response time: 51.5 days
90th percentile: 29.7 days
Tracked items: 35

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 226 days
Stale 30+ days: 4
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (9)
  • bug (6)
  • enhancement (6)
  • question (4)
  • Feature Request (2)
  • BC BREAK (1)
  • wontfix (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

GrumPHP is a PHP code-quality tool that integrates with Git hooks to enforce quality standards automatically.

The tool solves the problem of maintaining consistent code quality across a team by running quality checks before code is committed. It works by installing Git pre-commit hooks that execute a configurable set of PHP linters, code sniffers, and other quality checkers. When a developer attempts to commit code, GrumPHP runs these checks and blocks the commit if violations are found, forcing developers to fix issues before they enter the repository.

Teams should adopt GrumPHP when they want to shift quality enforcement left, catching problems during development rather than in code review or CI pipelines. It suits projects where developers use Git locally and benefit from immediate feedback on code quality. The tool works as a Composer plugin, making it straightforward to add to existing PHP projects. It is particularly valuable for teams that want to standardize which quality tools run and when, without requiring each developer to remember to run checks manually.

The project maintains active engagement with its codebase, regularly accepting and integrating contributions. Development shows responsiveness to issues raised by users, with maintainers addressing problems and reviewing pull requests. The project demonstrates a commitment to keeping the tool compatible with modern PHP tooling and practices through ongoing updates and refinements.