mdigi/laravel-jasper-client
Adoption is still minimal, and the repository has no security policy or scanning. A clear README, tests, MIT licensing, and a focused dependency set provide useful safeguards.
58%
Total Score
25
100
83
83
Health Score Breakdown
There were no commits and no active maintainers in the last three months, despite the repository being only about 163 days old. That makes ongoing maintenance uncertain.
The repository is owned by a personal GitHub account rather than an organization, so the available ownership evidence does not show institutional backing.
The package has four releases, all published within about 31 minutes, and no later release over its 163-day lifetime. This shows an early burst but not an established release cadence.
The repository has zero stars, forks, and watchers. This does not prove poor quality, but it provides no supporting evidence of community adoption.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap rather than proof of unsafe code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/http Version ^9.0|^10.0|^11.0|^12.0 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
illuminate/support Version ^9.0|^10.0|^11.0|^12.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 months 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.