MIT licensing and a usable README help with adoption, while the project has no security policy and only one registry maintainer. The codebase has been inactive since 2018, so compatibility and support are uncertain.
34%
Total Score
33
71
75
The package has had no registry releases in the last 12 months, and its latest recorded release was in September 2016. This long release gap is strong evidence of abandonment risk.
There were zero commits and zero active maintainers during the last three months, following a last repository push in 2018. This indicates a strong abandonment and support risk.
Only one registry account has publish access. That may be sufficient for a small user-owned project, but it leaves little visible publishing continuity or redundancy.
One issue and one pull request remain open, with no new or closed activity in the last month. This supports the broader picture of an inactive project, though it is not severe by itself.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap rather than a standalone severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
intervention/image Version 2.3.* | — | — |
league/flysystem-aws-s3-v3 Version 1.0.* | — | — |
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.