The tiny project footprint and absence of a security policy provide little support for long-term maintenance. Its tests, matching repository, declared license, and minimal dependencies make the release transparent, but not enough to offset the stale development history.
42%
Total Score
50
100
69
75
The package has made only 2 releases, both in July 2017, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency released roughly 9 years ago.
The repository is owned by a user account rather than an organization, so there is no demonstrated organizational backing to compensate for the small maintainer footprint.
The repository has 0 stars and 0 forks, with only 3 watchers. Popularity is not decisive by itself, but this provides little evidence of broad review or continued community support.
Composer is used for builds, but no security scanning tools are present. The missing scanning is a modest transparency and maintenance concern for a dependency.
The repository has no security policy. For a package intended to be shared as a dependency, this reduces transparency about how vulnerabilities would be reported and handled.
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.