goaop/goaop-laravel-bridge
Clear documentation, tests, licensing, and an active repository reduce adoption friction. Organization backing and read-only workflow permissions help, but pinning all five actions would improve build reproducibility.
68%
Total Score
83
100
88
67
Health Score Breakdown
The package is mature, but only five releases over more than 10 years and a median interval of about 803 days indicate a slow release cadence.
Recent activity is highly concentrated: one contributor made about 95% of commits, leaving a meaningful continuity risk despite a second contributor being active.
No repository security policy was found, which leaves vulnerability-reporting expectations less transparent.
Version 2.0.0-RC1 is a prerelease, so compatibility and support expectations are less settled than for a stable release.
Both workflows were analyzed without dangerous triggers or audit findings, and one uses read-only permissions; however, all five action references are unpinned, weakening reproducibility.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Lisachenko Alexander |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 goaop/framework Version ^4.0@dev | — | — |
illuminate/support Version ^12.0|^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 10 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.