pingiun/fix-composer-conflicts
The source is small and clearly structured, with tests and release notes for this version. Maintenance appears thin: one maintainer, no registry releases in the last 12 months, and no commits in the last 3 months; workflow references are also unpinned.
64%
Total Score
50
79
75
Health Score Breakdown
There is one registry maintainer. That is a thin publishing base for a user-owned project and increases continuity risk if that person stops maintaining it.
Only two releases were published on the same day, and there were no releases in the last 12 months. That suggests limited release maturity, although the package is still relatively young.
The repository had zero commits and zero active maintainers in the last 3 months. Combined with no registry releases in the last 12 months, this indicates currently quiet maintenance.
Composer is used for the build, but no security scanning tools are configured. For this small package that is a hygiene gap, not evidence of abandonment on its own.
The repository has no security policy. This weakens vulnerability-reporting transparency, although it does not by itself show that the package is unsafe to depend on.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jelle Besseling |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 composer/semver Version ^3.4 | — | — |
symfony/console Version ^7.3 | — | — |
symfony/process Version ^7.3 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 1 year 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.