The release is licensed, documented, stable, and supported by frequent recent publishing. No security policy or security scanning is visible, leaving fewer safeguards around changes and releases.
72%
Total Score
67
100
93
50
The repository is owned by the same individual namespace as the registry package, and the owner type is User rather than Organization. This is consistent ownership, but it does not provide organizational maintenance redundancy.
One contributor made all 24 commits in the last three months, giving the project a 100% top-contributor share. That concentration raises continuity risk despite the recent activity.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a modest supply-chain hygiene gap, not evidence that the release is unsafe.
The repository has no security policy. This reduces transparency about vulnerability reporting and response expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/config Version ^v13.33.0 | — | — |
illuminate/support Version ^v13.33.0 | — | — |
aedart/athenaeum-utils Version ^10.21 | — | — |
aedart/athenaeum-contracts Version ^10.21 | — | — |
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.