vimeo/psalm

A PHP static analysis tool for finding errors and security vulnerabilities in PHP applications

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 11th, 2026
Created on November 21st, 2016
Open Issues & Pull Requests: 2,106 (+0)
GitHub issues: Enabled
Number of forks: 709
Total Stargazers: 5,891 (+0)
Total Subscribers: 54 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Psalm is a static analysis tool for finding errors and security vulnerabilities in PHP applications.

Psalm catches bugs, type mismatches, and security issues by analyzing PHP code without executing it. The tool performs type inference across codebases to identify problems that would otherwise surface only at runtime or in production. It includes taint analysis capabilities for tracking potentially unsafe data flows through applications, helping developers spot security vulnerabilities before deployment.

Psalm suits teams building PHP applications where code quality and security matter. It works well integrated into development workflows and continuous integration pipelines. The tool is particularly valuable for large codebases where manual review becomes impractical, and for projects where security vulnerabilities carry high risk. Developers should expect to configure Psalm for their specific codebase, as the tool provides configuration options to tune analysis strictness and suppress false positives where needed.

The project maintains active engagement with its user base. Almost all open issues come from outside users rather than the core team, reflecting a substantial base of adopters relying on the tool in production. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on bug fixes, enhancements, and template improvements, showing a focus on stability and usability rather than experimental features.