A clear README, MIT licensing, and a matching repository improve transparency. Sparse tooling and no security policy leave little evidence of ongoing oversight.
40%
Total Score
50
83
50
The package has had no releases in the last 12 months, with the latest release published nearly seven years ago. This is strong evidence of abandonment risk, although the package is not marked deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. A non-archived repository does not compensate for the absence of observed maintenance.
Composer build tooling is present, but no security scanning tools were detected. The build setup is established, yet oversight evidence is limited.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap for a package used in applications.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.