vvb/max-laravel
A single publisher and no repository security policy leave limited evidence of long-term maintenance and oversight. The source includes tests, release notes, and a clear license, which partly offsets the project's early stage.
68%
Total Score
50
75
67
Health Score Breakdown
The package runs a post-autoload-dump lifecycle script during installation. This adds execution during dependency operations and warrants attention, although the signal does not show that the script is harmful.
Only one registry account, VVBphp, has publishing access. The linked repository is also owned by an individual account, so there is limited visible publishing and maintenance redundancy.
The repository owner is an individual account rather than an organization. That is not inherently unhealthy, but it provides less visible institutional backing for this young package.
The package is only 48 days old with two releases, spaced about 12 days apart. That shows active initial development but not enough history to establish durable maintenance.
The repository has zero stars, forks, and watchers. For a package only 48 days old this is not decisive, but it provides no independent evidence of adoption or community support.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 VVBphp |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/log Version ^3.0 | — | — |
guzzlehttp/guzzle Version ^7.0|^8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 1 month 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.