Tests, documentation, licensing, and a recent release support adoption. CI actions are unpinned, while maintenance is concentrated in one contributor with a modest release cadence.
72%
Total Score
50
92
67
Only one registry account has publish access. That is a genuine continuity concern for a user-owned project, although repository activity shows the same maintainer is still active.
The package has existed for about 6 years with 11 releases, but only one release in the last 12 months and a median interval of about 7.5 months indicate a modest cadence. The latest release is recent enough that this is a caution rather than abandonment evidence.
All three-month commit activity came from one contributor, giving the project a bus factor of one. The repository is user-owned, so there is no shown organizational handoff capacity to offset that concentration.
There was one commit from one active maintainer in the last three months. Recent activity exists, but the low volume provides limited evidence of sustained maintenance capacity.
The repository has no security policy. This is a transparency gap for reporting vulnerabilities, though it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mpyw/unclosure Version ^3.1 | — | — |
illuminate/support Version ^11.0 || ^12.0 || ^13.0 || ^14.0 | — | — |
illuminate/database Version ^11.0 || ^12.0 || ^13.0 || ^14.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.