The package has clear documentation, tests, release notes, and a long release history. Recent repository commits have stopped, and there is no security policy or scanning configuration.
68%
Total Score
67
100
93
83
There were no commits and no active maintainers in the three months before collection. Although the package released four times in the last year, the lack of recent repository work is a meaningful maintenance concern.
There are no new or closed issues in the last month and no merged pull requests, while four pull requests remain open. This reinforces the recent lack of visible maintenance activity, though it is less severe than an archived repository.
The repository uses Make and Composer, providing build tooling, but no security scanning tools were detected. That leaves security checks less transparent, without indicating that the package is unsafe.
No security policy was found in the repository. This is a transparency and vulnerability-reporting gap, but it is not evidence of malicious behavior or abandonment by itself.
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.