Laravel blade class directive
58%
Total Score
50
100
88
50
One individual has registry publish access, leaving a thin publishing base and little redundancy if that maintainer becomes unavailable.
Only two releases exist, with the latest on June 1, 2019 and no releases in the last 12 months. That long release gap reduces confidence that the package is actively maintained.
The repository had zero commits and zero active maintainers in the last three months, indicating currently sparse development activity.
Composer build tooling is present, but no security scanning tools were detected. For a small package this is a hygiene gap rather than a severe adoption blocker.
The repository has no security policy, so users are given no documented channel or process for reporting vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^5.8 | — | — |
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.