mesingh/laravel-messenger-mongo
The MIT license, readable documentation, and repository tests support inspection and integration. Missing security policy and scanning leave weaker safeguards around a project that has seen no recent activity.
34%
Total Score
0
75
75
Health Score Breakdown
The latest release was over 10 years ago, with no releases in the last 12 months. This is strong evidence that maintenance has stopped, despite a history of 39 releases.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity for over 10 years.
The repository name matches the package, reducing the risk of an unrelated source repository, but the README does not mention the package name explicitly. This creates a minor provenance concern.
Composer is used as a build tool, but no security scanning tool was detected. That weakens automated safeguards for a package with no recent maintenance activity.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, though it is less severe than the long-standing inactivity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Chris Gmyr |
| Dale Inverarity |
| Mandeep Singh |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 nesbot/carbon Version ~1.0 | — | — |
illuminate/config Version ~5.1 | — | — |
illuminate/support Version ~5.1 | — | — |
illuminate/database Version ~5.1 | — | — |
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 11 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.