catlabinteractive/laravel-charon
There is no security policy or automated security scanning, and registry publishing rests with one maintainer. A readme, tests, and release notes help, but they do not offset the long-term maintenance concern.
40%
Total Score
67
86
50
Health Score Breakdown
One registry maintainer publishes the package, which is a thin publishing base. The organization-backed repository provides some compensation, but does not show active release work.
Only two releases exist, and the latest was in January 2019, about seven years ago, with no releases in the last 12 months. This is a substantial abandonment concern.
The repository recorded zero commits and zero active maintainers in the last three months. Although it was pushed in 2022, current development activity is absent.
Composer build tooling is present, but no security scanning tools were detected. The build setup is adequate while security-process coverage is limited.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a REST API project.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Thijs Van der Schaeghe |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 laravel/tinker Version ^1.0 | — | — |
fideloper/proxy Version ^4.0 | — | — |
laravel/passport Version ^7.1 | — | — |
laravel/framework Version 5.7.* | — | — |
barryvdh/laravel-cors Version ^0.11.2 | — | — |
Weekly Downloads
Info
- Last Published
- 7 years 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.