Usable with caveats: the release is current, licensed, correctly backed by an unarchived repository, and has clear consumer documentation. However, it has only four releases, no recent repository activity, no tests or security policy, and a single registry publisher.
68%
Total Score
67
100
88
75
Only one account has registry publish access, which creates a narrow publishing path. The repository is organization-owned, providing some backing, but the registry still has limited observed publisher redundancy.
The package has existed for 1034 days but has only four releases, with one release in the last 12 months. The latest release was published about four months before collection, so maintenance is present but limited.
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the package's small release history, this raises concern about how quickly issues or compatibility changes will be handled.
The repository uses Composer for its build tooling, but no security scanning tool was detected. The build setup is appropriate for the package, while the missing scanning is a modest transparency gap.
The repository has no security policy. For a driver that stores audit data in Elasticsearch, the absence of documented vulnerability-reporting guidance is a genuine security-maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
owen-it/laravel-auditing Version ^13.5 || ^14.0.1 | — | — |
elasticsearch/elasticsearch Version 7.* | — | — |
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.