The package has clear documentation, an MIT declaration, and a matching source repository. Its six releases arrived within about one day, while the repository shows no commits in the last three months and has no security policy or scanning tools.
62%
Total Score
50
100
88
75
The package and repository are owned by the same individual account. This provides direct ownership alignment, but not the broader maintenance capacity of an organization-backed project.
All six releases were published within about one day, with a median interval of roughly 18 minutes. This shows active initial publishing but provides little evidence of sustained maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. That is a meaningful maintenance concern for a young package despite the recent push associated with its initial releases.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy. For a package that handles API tokens and webhook data, the missing reporting guidance weakens project transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0|^11.0|^12.0 | — | — |
illuminate/routing Version ^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0 | — | — |
illuminate/database Version ^10.0|^11.0|^12.0 | — | — |
illuminate/contracts Version ^10.0|^11.0|^12.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.