Documentation and the MIT licensing are in place, with a small runtime dependency set. However, the project has had no recent commits or issue activity, lacks a security policy, and the repository does not clearly identify this package.
43%
Total Score
25
100
75
50
The last registry release was in October 2020, and there were no releases in the following 12 months, indicating prolonged release inactivity for a framework integration package.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long gap since the last release and raising abandonment risk.
There were no new or closed issues and no merged pull requests in the last month; six open issues and one open pull request show unresolved maintenance demand.
The linked repository name does not match the package name and its README does not mention this package, so the package-to-source relationship is not clearly established. The organization backing and package structure provide some context but do not remove this transparency gap.
Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
payum/core Version ^1 | — | — |
illuminate/routing Version ^4|^5.1|^6.0|^7.0|^8.0 | — | — |
illuminate/support Version ^4|^5.1|^6.0|^7.0|^8.0 | — | — |
illuminate/container Version ^4|^5.1|^6.0|^7.0|^8.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.