Its MIT license, focused dependency set, tests, and organization backing make the package straightforward to assess and maintain in principle. The long period without releases or commits leaves compatibility and abandonment concerns for a prerelease dependency.
58%
Total Score
50
100
79
83
There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push more than eight years ago. This materially raises abandonment and unmaintained-compatibility risk.
The package has only two releases, with none in the last 12 months; its latest release was published more than eight years ago. This is strong evidence of stagnation, though the package's narrow scope may reduce the need for frequent releases.
There were no new or closed issues or pull requests in the last month, and no items are currently open. The clean tracker is mildly reassuring, but it does not offset the absence of recent development.
The repository uses Composer for builds, but no security scanning tools were detected. The missing scanning is a hygiene limitation, not evidence that the small package is unsafe to depend on.
No security policy was found in the repository. This weakens vulnerability-reporting transparency, although the package's narrow interface scope and minimal runtime dependencies partly limit the practical concern.
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.