42%
Total Score
unhealthy
Risky: no release or commit activity since March 2018, and it remains at v0.1.
The package has made only one release, on March 28, 2018, with no releases in more than 8 years. This is strong evidence of abandonment for a dependency whose compatibility may need maintenance.
The repository has had zero commits and zero active maintainers in the last 3 months, and its last push was in March 2018. This confirms that the long release gap reflects inactive development.
Only one registry publisher is listed, which would be a limited publishing base. The organization-owned repository provides some backing, so this is a modest concern rather than a severe one.
Composer build tooling is present, but no security scanning tooling is reported. The missing scanning is a hygiene gap and does not outweigh the much stronger maintenance evidence.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This matters for a package that interacts with application databases.
We didn't find any vulnerabilities for this package.
| Version | Published | Vulnerabilities |
|---|---|---|
| v0.1 | 27 Mar 2018 | 0 0 critical, 0 total 0 0 high, 0 total 0 0 medium, 0 total 0 0 low, 0 total |
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version 5.*.* | — | — |
illuminate/support Version 5.*.* | — | — |
illuminate/database Version 5.*.* | — | — |
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.