The package has clear licensing, documentation, tests in the repository, and a matching source project. Its tiny maintainer and user base, no commits for nearly three years, and stale release history make future fixes uncertain; workflow checks also need tightening.
52%
Total Score
38
100
75
50
Only two releases exist, with none in the last 12 months; the latest release was published more than three years ago. This is meaningful abandonment risk for a dependency that may need compatibility fixes.
There were no commits and no active maintainers during the last three months, consistent with the repository having seen no meaningful activity since 2023.
One registry maintainer is consistent with a user-owned project, but it leaves little visible redundancy if that maintainer stops supporting the package.
The repository is owned by an individual account rather than an organization, so the single-maintainer and limited-backing concerns are relevant.
There are no new or closed issues or pull requests in the last month, and two pull requests remain open. This suggests limited ongoing project response.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spatie/fork Version ^1.1 | — | — |
illuminate/contracts Version ^9.0 || ^10.0 | — | — |
spatie/laravel-package-tools Version ^1.13.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.