The package includes tests, a README, a changelog, and matching MIT licensing. Organization backing and recent commits help, but the small, concentrated contributor base and repository-name mismatch leave meaningful adoption risk.
67%
Total Score
83
83
75
The package is only 45 days old, with 12 releases clustered over about two days. This shows active initial development but provides little evidence of long-term maintenance stability.
Two contributors are active, but the leading contributor made 83% of recent commits. Organization backing partly offsets this concentration, but the active maintainer base remains thin.
The repository name does not match the package name and its README does not mention the package. Although the repository may be a related module, this weakens confidence that the source repository directly corresponds to the published package.
The repository has no security policy. This is a transparency and incident-handling gap, although it is not by itself evidence that the release is unsafe.
All three workflows were analyzed with no reported audit findings, unsafe trigger sinks, or write-wide permissions. However, all three action references are unpinned, leaving avoidable workflow reproducibility and dependency drift risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^13.0 | — | — |
illuminate/support Version ^13.0 | — | — |
illuminate/contracts Version ^13.0 | — | — |
liberusoftware/module-manager Version ^1.0 | — | — |
liberusoftware/localization-contracts Version ^1.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.