ernestdefoe/picks
Healthy and actively maintained, with a clear license, tests, matching repository, and recent commit activity. The main caveats are a small maintainer base, no security policy or security scanning, and a workflow with write permissions.
82%
Total Score
63
100
89
80
Health Score Breakdown
Only one registry account has publish access, which is a genuine publishing continuity concern for a user-owned project, although repository activity shows another active contributor.
The registry namespace and repository are owned by the same individual user rather than an organization, so there is no organizational backing to offset the small maintainer base.
Commit activity is evenly split between two contributors, so no single contributor dominates the recent history; the small total contributor base still leaves limited redundancy.
The repository has zero stars, forks, and watchers, limiting external validation and community support; this is supporting evidence rather than a decisive health failure.
Composer is used as a build tool, but no security scanning tools are configured, leaving a security-maintenance gap that is relevant for a package with application and frontend code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Ernestdefoe |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 flarum/core Version ^2.0.0-beta.8 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
intervention/image Version ^3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 days ago
- Created
- 4 months 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.