Tests, documentation, release notes, and a matching source repository provide useful transparency. The small project footprint and workflow pinning leave less protection than mature alternatives.
62%
Total Score
50
100
89
50
One registry maintainer creates a thin publishing base, although the linked repository is owned by the same individual, so this is a modest rather than severe concern.
The repository is owned by an individual rather than an organization, so there is no visible organizational backing to offset the thin maintainer base.
The repository recorded zero commits and zero active maintainers in the last three months, which raises maintenance and abandonment risk despite the recent release.
Twelve stars and two forks indicate a small community and limited outside support; this is supporting caution rather than a verdict by itself.
Composer build tooling is present, but no security scanning tools were detected, leaving a transparency and maintenance gap for a package that handles database credentials and API access.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.8 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
illuminate/database Version ^11.0|^12.0|^13.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.