Usable with caveats: the release is well documented, tested, licensed, and backed by a matching repository, but recent development has stopped and the project relies on one publisher.
72%
Total Score
50
100
100
90
Only one account has registry publishing access. The linked repository is user-owned rather than organization-owned, so this represents a genuine continuity and bus-factor concern.
The registry namespace and repository owner match, but the owner is an individual account rather than an organization, so there is no organizational backing to offset the single-maintainer risk.
The repository recorded zero commits and zero active maintainers during the last three months. Although a release and repository push occurred earlier in the year, the current lack of development activity raises maintenance risk.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, but it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
php-http/httplug Version ^2.4 | — | — |
owen-it/laravel-auditing Version ^13.0|^14.0 | — | — |
elasticsearch/elasticsearch Version ^8.0|^9.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.