The package has a clear README, tests, a matching repository, and a documented release. Its small single-person project has limited activity and lacks security scanning, while workflow dependency pinning needs improvement.
68%
Total Score
75
100
89
83
One registry account publishes the package. Because the repository is user-owned and the source shows a coherent project, this is a modest capacity concern rather than evidence of abandonment by itself.
The package has five releases over about two years, but none in the last 12 months and the latest release was over 13 months ago. This indicates a meaningful maintenance slowdown, though the release history is not empty.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with no releases in the last 12 months, this supports a caution about currently slow maintenance.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap, not a severe dependency risk on its own.
The repository has no security policy. For a small Blade-focused package this reduces vulnerability-reporting transparency, but it is not by itself evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^10|^11|^12 | — | — |
illuminate/contracts Version ^10|^11|^12 | — | — |
leuverink/asset-injector Version ^3.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.