The MIT license, one runtime dependency, and a matching non-archived source repository make the package reasonably transparent. Its last release and repository push were over eight years ago, with no commits in the past three months, so maintenance risk is substantial.
45%
Total Score
0
100
60
50
The package has had only three releases, with the latest published over eight years ago and none in the past 12 months. This is strong evidence of abandonment risk despite the previously regular 21-day release interval.
The repository recorded zero commits and zero active maintainers in the past three months, consistent with the package's long release silence. No provided maintenance signal compensates for this inactivity.
The artifact includes a README and the package has a GitHub release for this version. Missing tests and a changelog in the published artifact are normal packaging practice, but the README's documented API version predates this release and weakens documentation freshness.
Composer is used for builds, which supports reproducible package management, but no security scanning tool is present. This is a secondary transparency gap compared with the much stronger inactivity signal.
The linked repository has no security policy. That limits guidance for reporting vulnerabilities, although it is less significant than the package's prolonged lack of maintenance.
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.