neo4j/laravel-boost
Healthy and reasonable to depend on. It has frequent stable releases, recent work from three contributors, strong documentation and tests, and organization backing; the main gaps are the absence of a security policy and explicit workflow token permissions.
86%
Total Score
100
100
94
67
Health Score Breakdown
Composer build tooling is present, but no security-scanning tool was detected. The missing scanning is a transparency and assurance gap, though it is not by itself evidence of unsafe maintenance.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
All three analyzed workflows lack top-level token permissions. None declares top-level write access, but explicit least-privilege permissions would make the CI configuration more transparent.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 laravel/boost Version ^2.0 | — | — |
laravel/framework Version ^12.0|^13.0 | — | — |
laudis/neo4j-php-client Version ^3.4 | — | — |
Weekly Downloads
Info
- Last Published
- 16 days ago
- Created
- 5 months 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.