The repository has no security policy and does not clearly mention this package; its tiny README offers little consumer guidance. The MIT declaration, clean install scripts, and organization ownership provide limited reassurance.
38%
Total Score
75
70
75
The package has had no release in nearly six years and none in the last 12 months, despite only four releases overall. This is a substantial maintenance concern for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but that does not offset the lack of observed activity.
The repository name does not match the package name and its README does not mention the package, making package ownership or source alignment less transparent. Organization ownership provides some context but does not resolve the mismatch.
Composer build tooling is present, but no security scanning tools were detected. For an old, inactive package this adds a modest maintenance concern rather than a severe risk on its own.
The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though it is not evidence of malicious behavior.
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.