The MIT license, useful documentation, and matching source repository support transparency. The absence of security scanning and an active issue response adds maintenance risk for a package this old.
42%
Total Score
25
75
75
The latest release was published in June 2016, with no releases in the last 12 months. This long period without releases is strong evidence of abandonment risk, despite 14 releases earlier in the project's life.
The repository had zero commits and zero active maintainers in the last three months, while the latest push dates to June 2016. This is a substantial abandonment risk.
There are six open issues but no new or closed issues and no pull requests in the last month. This supports the broader evidence that maintenance is inactive.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene concern, especially alongside the project's long inactivity.
The repository has no security policy. That weakens vulnerability-reporting transparency, although it is less serious than the clear evidence of inactive maintenance.
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.