The MIT license, matching repository, clear README, and minimal dependency profile make the package easy to inspect and integrate. Its only release and repository activity are over eight years old, with no tests or security scanning, so compatibility and maintenance risk are substantial.
42%
Total Score
33
100
79
88
The package has only one release, 1.0.0, published over eight years ago, with no releases in the last 12 months. This provides little evidence of ongoing compatibility maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long period without releases. No newer activity is provided to offset the abandonment concern.
One registry account publishes the package. A single maintainer is not inherently unhealthy for a small module, but no broader maintainer base is shown to offset the long inactivity.
The repository is owned by an individual account rather than an organization. Together with a single registry maintainer, this indicates limited visible project backing and leaves less evidence of continuity.
Composer build tooling is present, which fits the package ecosystem, but no security scanning tools are configured. This is a hygiene weakness that adds to the transparency concern without proving the package is unsafe.
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.