Clear documentation, repository tests, an MIT license, and Dependabot coverage support adoption. The short release history and one-person recent commit base make long-term continuity less certain.
58%
Total Score
67
100
94
50
The package is about 502 days old with three releases and a median interval of about 219 days, indicating a relatively slow release cadence. A release within the assessed period provides some evidence of ongoing maintenance, but the history is still limited.
One contributor made 100% of the three recent commits. Organization ownership offers some handoff capacity, but no second active contributor is shown to demonstrate that capacity in practice.
There were three commits in the last three months, showing some recent activity, but all were made by one active maintainer. That is a thin maintenance base and raises continuity concerns.
The repository has no security policy. This is a modest transparency gap for a package that makes HTTP API requests, though it is not evidence of abandonment or unsafe behavior by itself.
The audit found a high-confidence bot-conditions issue in the Dependabot auto-merge workflow and all 12 analyzed action references are unpinned. The pull_request_target workflow has no untrusted checkout or script-injection finding, so these are workflow-hygiene concerns rather than a severe standalone risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spatie/laravel-data Version ^4.15 | — | — |
illuminate/contracts Version ^10.0||^11.0||^12.0||^13.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.