A single user-owned maintainer and minimal repository security practices leave limited resilience if development stops. The package is documented, licensed, not deprecated, and has a matching source repository, but its release activity has gone quiet.
55%
Total Score
50
100
78
75
The package has had no release in nearly two years, despite nine releases concentrated in its first 12 days; this is a meaningful maintenance and abandonment concern.
Only one registry maintainer is listed, and project_backing identifies a user-owned repository rather than an organization; this limits visible continuity if that maintainer stops work.
The repository has one star and no forks, so there is little external adoption evidence to compensate for the inactive release history; popularity is supporting evidence only.
Composer build tooling is present, but no security-scanning tooling is reported, leaving a modest transparency and maintenance gap.
The linked repository has no security policy, reducing clarity about vulnerability reporting and response expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^10.0 | — | — |
jackiedo/dotenv-editor Version ^2.1.0 | — | — |
spatie/laravel-markdown Version ^2.3 | — | — |
spatie/laravel-package-tools Version ^1.14.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.