otobank/phpstan-doctrine-criteria
The MIT license, matching repository, clear README, and comprehensive tests make the package easy to inspect and integrate. Maintenance is thin, with no commits in the last three months, infrequent releases, no security policy, and all six workflow actions unpinned.
62%
Total Score
75
78
83
Health Score Breakdown
The package has existed since February 2019 and has eight releases, but only one release in the last 12 months and a median interval of about 293 days indicate a slow cadence.
The repository recorded zero commits and zero active maintainers in the last three months, showing limited recent maintenance capacity.
Two stars and one fork indicate a small user base, but popularity is supporting evidence and does not outweigh the package's clear source and tests.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest security-process gap.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Toshiyuki Fujita |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 phpstan/phpstan Version ^1.12 | — | — |
nikic/php-parser Version ^4.13 | — | — |
doctrine/collections Version ^1.8 | — | — |
doctrine/persistence Version ^2.5 | — | — |
phpstan/phpstan-doctrine Version ^1.5 | — | — |
Weekly Downloads
Info
- Last Published
- 7 months ago
- Created
- 7 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.