The MIT license, matching repository, and organization backing improve transparency. The README is only 28 characters, while the repository has no security policy or scanning, leaving limited guidance and assurance.
40%
Total Score
50
58
50
The package has had no release in more than 8 years: its latest release was October 31, 2017, and it has had none in the last 12 months. This is strong evidence of abandonment despite four total releases.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with its last push occurring in October 2017. There is no provided evidence of current maintenance capacity.
The package includes a README, but it contains only 28 characters and offers little consumer guidance. Missing tests and a changelog are normal for published artifacts, while the GitHub release history provides some release transparency.
Composer build tooling is present, but no security scanning tools were detected. For a small extension this is a modest assurance gap, not evidence of maliciousness or an unsafe dependency by itself.
The repository has no security policy, so there is no documented channel or process for reporting vulnerabilities. This adds a transparency and maintenance concern, although it is less severe than the prolonged inactivity.
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.