MIT licensing, one runtime dependency, and no install scripts keep adoption straightforward. The lack of a security policy or scanning leaves safeguards weak, despite clear package ownership and a matching repository.
43%
Total Score
50
100
67
75
The package has only two releases, with the latest published in May 2016 and no releases in the last 12 months. This long release gap is a strong maintenance concern for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring years ago. That indicates little current maintenance capacity.
The linked repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no additional community signal to offset the inactivity.
Composer is used as a build tool, but no security-scanning tools are configured. The build setup is present, while automated security coverage is absent.
No security policy was found in the repository. This weakens vulnerability-reporting transparency, though it is a secondary concern compared with the clear maintenance gap.
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.