The small dependency surface and clear MIT licensing reduce integration friction. Pinning 1.0.1 is prudent because maintenance and security evidence have effectively stopped.
45%
Total Score
0
100
71
50
Only two releases exist, and none were published in the last 12 months; the latest release was in September 2020, nearly six years ago. This is strong evidence of abandonment risk, though the package is not deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the nearly six-year release gap. No newer activity compensates for this maintenance concern.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide no community-maintenance cushion.
Composer is used for the build, but no security-scanning tools are present. The missing scanning is a hygiene gap that adds to the package's limited maintenance evidence.
The repository has no security policy, leaving no documented process for handling vulnerability reports. This matters more for a framework integration package than it would for a purely internal utility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ~6.0 | ~7.0 | ~8.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.