The package has an MIT license, a usable README, tests, and a repository that matches its name. Composer install-time scripting and the lack of a published security policy leave some transparency and installation-risk concerns.
62%
Total Score
50
79
50
The package runs a post-autoload-dump Composer lifecycle script during installation. Such scripts can be legitimate, but they expand install-time behavior and warrant caution when the package has limited maintenance history.
The repository is owned by an individual account rather than an organization. That is not inherently unhealthy, but it indicates a thinner backing structure when paired with limited release and commit history.
The package has only one release over roughly 11 months, so there is little evidence of sustained release maintenance or version evolution.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the single-release history, this weakens evidence of ongoing maintenance.
The repository uses Composer build tooling, but no security-scanning tools were detected. This is a hygiene gap, though the absence of scanning alone does not indicate abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
backpack/crud Version dev-store | — | — |
laravel/framework Version ^12.0 | — | — |
parabellumkoval/request-data Version 0.1.x-dev | — | — |
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.