Usable with caveats: the package is transparent, licensed, tested in its repository, and actively being published, but it is only one day old and explicitly beta. Its single-maintainer foundation, absent security policy, and limited demonstrated history make it a risky choice for production billing without careful validation.
62%
Total Score
50
86
67
The package is only 1 day old with 3 releases, all published within roughly 21 hours, so there is not yet enough history to demonstrate sustained maintenance or production maturity.
There were 0 commits and 0 active maintainers in the prior 3 months, although the repository is only 1 day old. This is primarily a lack of historical evidence rather than proof of abandonment, but it lowers confidence in sustained maintenance.
No security policy was found in the repository. For a package handling recurring payment data, this is a transparency gap, even though it is not by itself evidence of unsafe code.
The repository's single workflow has no top-level token permissions declaration. No write permissions were observed, but explicitly restricting workflow tokens would provide stronger CI security hygiene.
Version v0.11.0 is not a stable major release, and the package's available documentation describes the project as beta with an API that may change before 1.0. That is a meaningful compatibility risk for a billing integration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
creagia/redsys-php Version ^3.0 | — | — |
illuminate/console Version ^12.0|^13.0 | — | — |
illuminate/support Version ^12.0|^13.0 | — | — |
illuminate/database Version ^12.0|^13.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.