lipemat/phpstan-wordpress
The MIT license, repository tests, and release notes make the package easier to inspect and integrate. A single active maintainer, missing security policy, install-time scripts, and broad unpinned release-workflow settings add modest continuity and build-hygiene concerns.
78%
Total Score
67
100
50
Health Score Breakdown
Composer post-install and post-update scripts run during dependency operations, adding execution behavior that consumers should understand before adoption.
The package and repository are owned by the same individual account, so there is no organization backing shown to offset the concentrated contributor base.
One contributor made all 9 commits in the last 3 months, leaving maintenance dependent on a single individual and increasing continuity risk.
The repository has no security policy, reducing transparency about how maintainers expect vulnerabilities to be reported and handled.
The single analyzed workflow has top-level write permissions and its one action reference is unpinned. No untrusted checkout, script injection, or auditor findings were detected, so this is a modest hygiene concern rather than a severe risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 phpstan/phpstan Version ^2.2.14 | — | — |
php-stubs/wp-cli-stubs Version ^2.12.0 | — | — |
phpstan/extension-installer Version ^1.4.3 | — | — |
szepeviktor/phpstan-wordpress Version ^2.0.4 | — | — |
Weekly Downloads
Info
- Last Published
- 23 hours 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.