igritsay/phing-tools
The artifact is extremely small and offers little guidance for consumers. Its single runtime dependency and lack of install-time scripts keep complexity low, but do not make up for the limited project evidence.
36%
Total Score
50
100
56
67
Health Score Breakdown
The latest release was published in July 2015, and there have been no releases in more than 11 years. This strongly indicates abandonment risk despite four historical releases.
The package declares no license, contains no license file, and the repository has no license file. This creates a real legal and transparency barrier to depending on it.
Only one registry maintainer account is listed. Because the project is backed by an individual rather than an organization, this leaves a thin publishing and continuity base.
Only five files are present, consisting mainly of build metadata, composer.json, and one PHP class. That may fit a narrowly focused tool, but it provides little evidence of testing, documentation, or project maturity.
The artifact has no README, tests, or changelog, while the repository also has no tests or changelog. The GitHub release marker is a small positive, but it does not provide consumer documentation or meaningful maintenance evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 igritsay |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 phing/phing Version * | — | — |
Weekly Downloads
Info
- Last Published
- 11 years ago
- Created
- 11 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.