35%
Total Score
unhealthy
Risky: no release or repository activity since March 2016 makes abandonment the main concern.
Only one account has registry publish access. That is not evidence of unsafe administration, but it provides little publishing redundancy for a long-unmaintained package.
The registry and repository are owned by the same individual account, providing a consistent ownership link but no organizational backing that would compensate for the thin maintenance base.
The package has had 57 releases since March 2016, but none in the last 12 months and no release activity for about 10 years. That strongly raises abandonment risk.
There were zero commits and zero active maintainers in the last three months, consistent with the long gap since the last push and materially increasing abandonment risk.
The repository has zero stars and forks and one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of an active user or contributor community.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ~5.0 | — | — |
illuminate/session Version ~5.0 | — | — |
illuminate/support Version ~5.0 | — | — |
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
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.