The single-file artifact has no README, while the repository has no security policy or scanning. Its MIT declaration, minimal PHP dependency set, and clean non-archived status reduce operational concerns, but five years without activity remains the main risk.
38%
Total Score
0
100
67
75
The package has had only three releases, all clustered between January 24 and January 25, 2021, with no releases in the last five years. That strongly indicates abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.
The package has no README, which is a real consumer-documentation gap for a library; the absence of tests and a changelog is normal for a published artifact and is not penalized.
Composer is used for the build, but no security scanning tools are configured. That weakens maintenance hygiene for a dependency, despite the simple package structure.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, though not evidence of a security incident.
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.