The two-file artifact provides little consumer documentation, and the repository has no security scanning or policy. Its MIT declaration and lack of install scripts reduce exposure but do not offset the maintenance risk.
20%
Total Score
0
58
67
The package has only one release, published about 12 years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long period since its only release. No provided activity signal compensates for this.
The package contains only two files, a client class and composer.json. This may be intentionally minimal, but it provides little visible project context or consumer guidance for a library.
The artifact has no README, tests, changelog, or release notes. Missing tests and changelog are normal for published artifacts, but the absent README is a real documentation gap for a library consumers must integrate.
Composer is used as the build tool, but no security scanning tools are configured. This weakens ongoing maintenance hygiene and is not offset by another security signal.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.