The package includes a README, repository tests, and an MIT license. Its source project has no security policy or scanning, adding transparency concerns to the otherwise limited maintenance evidence.
35%
Total Score
75
50
50
The package has only four releases, all clustered in February 2013, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency released as v0.1.5.
The repository is not formally archived, but it was last pushed in April 2014—more than 12 years before this assessment. The unarchived status does not compensate for the long period without observed activity.
There were no new or closed issues or pull requests in the last month, and no open issues or pull requests. This is consistent with an inactive project, though issue counts alone are weaker evidence than release and commit history.
The repository name does not match the package name and its README does not mention the package. Although this can occur with subpackages, the missing reference makes package-to-source ownership less transparent.
Composer is used for the build, but no security-scanning tooling was detected. This does not prove unsafe dependencies, but it reduces evidence of ongoing maintenance hygiene.
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.