Testing, documentation, and licensing make integration clearer. The project has had no commits or releases for over six years, and its repository shows no community activity; the missing security policy adds a smaller transparency gap.
55%
Total Score
50
88
75
The package has 32 releases but none in the last 12 months, with the latest release over six years ago. That long pause materially raises abandonment risk despite the established release history.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release hiatus. This is the strongest evidence that ongoing maintenance capacity is limited.
There were no new or closed issues or pull requests in the last month, and no pull requests were merged. This provides little evidence of an active community or current upkeep.
The repository has zero stars, forks, and watchers, so there is little visible external adoption or review to compensate for the lack of recent maintenance. Popularity is supporting evidence rather than decisive on its own.
The repository has no security policy, leaving no documented channel or process for reporting security issues. This is a modest transparency gap, though it is less serious than the maintenance slowdown.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/semver Version ~1.4 | — | — |
illuminate/view Version ~5.0|~6.0|~7.0 | — | — |
illuminate/support Version ~5.0|~6.0|~7.0 | — | — |
illuminate/contracts Version ~5.0|~6.0|~7.0 | — | — |
illuminate/filesystem Version ~5.0|~6.0|~7.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.