The package has a clear README, an MIT declaration, and a small, focused dependency set. Its source repository is identifiable and not archived, but maintenance transparency is limited by no recent commits and no published security policy.
58%
Total Score
67
100
83
50
A single registry publishing account is consistent with this user-owned repository, but it leaves little visible publishing redundancy if that maintainer becomes inactive.
The package has only two releases, both from May 2022, with no releases in the last 12 months; this is strong evidence of limited ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the concern that active maintenance has slowed or stopped.
The repository has zero stars and forks and one watcher, offering little community evidence; popularity is supporting evidence, so this only modestly lowers confidence in project maturity.
Composer is used for the build, which fits the package ecosystem, but no security-scanning tooling is present; this is a transparency and hygiene gap rather than a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^9.0 | — | — |
illuminate/container Version ^9.0 | — | — |
andrewdevelop/hex-contracts Version ^2.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.