The package has a clear MIT license, tests, documentation, and a matching source repository. However, its last registry release was over nine years ago and the repository has had no recent commits or issue activity, leaving compatibility and maintenance risks.
42%
Total Score
33
80
75
The latest release was over nine years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a library dependency.
The repository recorded 0 commits and 0 active maintainers in the last three months, confirming that maintenance has stopped rather than merely slowing.
The package and repository are owned by the same individual account. This provides identity consistency, but no organizational backing to compensate for the inactive project.
There were no new or closed issues or pull requests in the last month, while 6 issues remain open. This provides no evidence of active support.
The repository has no security policy. This is a transparency gap for a package that handles encryption, although the available license, tests, and source repository provide some compensating visibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/config Version ^5.0 | — | — |
illuminate/console Version ^5.0 | — | — |
illuminate/support Version ^5.0 | — | — |
illuminate/container Version ^5.0 | — | — |
illuminate/contracts Version ^5.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.