The repository includes a substantial README, a test suite, and a clear package structure. Its young age, single-person ownership, and lack of recent commits leave ongoing support uncertain.
58%
Total Score
50
78
75
The registry lists one maintainer, and project backing identifies a personal repository rather than an organization. This leaves limited visible ownership redundancy, though registry access alone does not measure actual activity.
The package is only 110 days old, with all 8 releases arriving on the same day and a median interval of about 10 minutes. This shows active initial publishing but not an established maintenance pattern.
The repository recorded 0 commits and 0 active maintainers in the last three months. For a package only 110 days old, that is a meaningful maintenance concern.
The repository has 0 stars, forks, and watchers. This is weak supporting evidence for maturity, but it is not by itself evidence that the package is unsafe to depend on.
Composer build tooling is present, but no security-scanning tools were detected. That is a transparency and maintenance gap rather than a severe risk on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/view Version ^8.0|^9.0|^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^8.0|^9.0|^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/contracts Version ^8.0|^9.0|^10.0|^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.