wilkques/console
The repository includes extensive tests and clear upgrade guidance. Dependencies and install behavior are straightforward, but the workflow lacks pinned actions and security scanning.
70%
Total Score
67
100
94
67
Health Score Breakdown
The repository is owned by a user rather than an organization, so the single-contributor concentration has no visible organizational handoff support.
One contributor made all six commits in the last three months, giving the project a concentrated maintenance base. That creates continuity and handoff risk for a user-owned project.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap, not evidence of unsafe code.
The repository has no security policy. This weakens the process for reporting and handling vulnerabilities, although it does not by itself indicate abandonment.
The sole workflow was fully analyzed with no dangerous triggers or audit findings, but all three action references are unpinned. That leaves CI exposed to upstream action changes and is a manageable hygiene concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 wilkques/container Version >=5.0.0 | — | — |
wilkques/filesystem Version >=1.0.1 | — | — |
wilkques/php-helper Version ^6.1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 22 hours ago
- Created
- 3 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.