Risky to adopt for new projects: the package has had no release or repository activity since August 2015, with only one release and no active contributors. Its small scope, clear README, MIT license, and minimal dependency keep it usable, but abandonment risk is substantial.
48%
Total Score
25
72
88
The package has only one release, published in August 2015, and none in the past 12 months. This is strong evidence of long-term inactivity and lowers confidence that defects or compatibility issues will be addressed.
There were no commits and no active maintainers in the last three months, consistent with the repository's last activity being in August 2015. This is the main reason the package falls below the healthy band.
The repository is owned by an individual account rather than an organization, and the registry namespace differs from the repository owner. This does not prove a problem, but it provides limited visible backing for a project that has been inactive for years.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide no meaningful community or adoption buffer for the stale project.
Composer is used as a build tool, which fits the package ecosystem, but no security scanning tools are present. For this small, old package that is a transparency gap, though it is less serious than the lack of maintenance activity.
We didn't find any vulnerabilities for this package.
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.