Its MIT licensing, tests, changelog, and matching source repository provide useful transparency. The four-year release gap and zero recent commits make long-term support uncertain; pin this version only if you can maintain the CMS yourself.
43%
Total Score
25
75
75
The latest release was about four years ago, with no releases in the last 12 months. Although the package had 216 releases historically, the prolonged release gap indicates likely abandonment risk.
The repository recorded zero commits and zero active maintainers during the last three months. This reinforces the release gap and leaves no evidence of ongoing maintenance.
There were no new or closed issues in the last month, and 24 pull requests remain open. Combined with zero recent commits, this suggests unresolved project activity rather than active maintenance.
Composer build tooling is present, but no security scanning tools were detected. The build setup is appropriate, while the missing security tooling is a modest transparency gap.
The repository has no security policy and no security scanning tools were reported. This weakens vulnerability-reporting and security-maintenance transparency, though it is secondary to the inactivity evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/dbal Version ^2.10 | — | — |
jzpeepz/dynamo Version @dev | — | — |
laravel/framework Version ^6.0|^7.0|^8.0 | — | — |
laravelcollective/html Version ^6.0 | — | — |
spatie/laravel-medialibrary Version ^7.0.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.