richcongress/static-analysis
The package is clearly licensed, documented, and recently released, with no deprecation or install-time scripts. Maintenance is thin: there has been no commit activity in three months, and registry publishing is handled by one maintainer; the repository also has no security scanning.
68%
Total Score
75
100
83
75
Health Score Breakdown
Only one account has registry publishing access. The organization-backed repository provides some context, but the registry still has a thin publishing base.
The repository recorded zero commits and zero active maintainers in the last three months. This is a concrete maintenance concern, although the recent release partly offsets the risk.
The repository has no stars or forks and one watcher. Popularity is only supporting evidence, so this modest reach lowers confidence in community support but is not decisive for a small tooling package.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, reducing transparency about how vulnerability reports are handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Nicolas Guilloux |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 phpstan/phpstan Version ^2.0 | — | — |
phpmetrics/phpmetrics Version ^2.7 || ^3.0 | — | — |
friendsofphp/php-cs-fixer Version ^2.0 || ^3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 months ago
- Created
- 5 years ago
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.