The small, clearly packaged codebase has a README, MIT licensing, a stable release, and no install-time scripts. Missing security policy and dormant repository activity reduce transparency and confidence in ongoing maintenance.
65%
Total Score
50
89
83
The package has existed since December 2016 with 12 releases, but it has had no releases in the last 12 months and its latest release was about 20 months ago. This lowers confidence in ongoing maintenance, despite its established history.
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the long release gap, this is a meaningful maintenance concern.
There are nine open issues, but no new or closed issues and no pull-request activity in the last month. This is consistent with a quiet maintenance state and modestly increases abandonment concern.
Composer is used as the build tool, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.
No security policy was found in the repository, leaving vulnerability-reporting expectations undocumented. This reduces transparency for a dependency that is otherwise clearly identified and licensed.
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.