bryangruneberg/laragoon
There is no security policy or repository security scanning, which leaves maintenance practices less transparent. The package is clearly licensed, documented, and has release notes for this version, but those strengths do not offset its age.
42%
Total Score
50
70
75
Health Score Breakdown
The package has had no release in nearly six years, despite 13 releases overall; this is strong evidence that maintenance has stopped.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long gap since the last release.
There were no new or closed issues or pull requests in the last month, consistent with an inactive project rather than an actively maintained one.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Bryan Gruneberg |
| Blaize Kaye |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 amazee/laragoon-support-libs Version ^0.1 | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 8 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.