The package has a clear README, a matching repository, and no install-time scripts. Its single-person ownership and limited project history leave little evidence of sustained support for a security-focused library.
60%
Total Score
50
83
75
The registry lists one maintainer, and the repository is owned by an individual rather than an organization. This gives the project a thin support base, although the matching repository confirms clear ownership.
Only two releases were published on the same day, followed by no new release for 179 days. That is limited evidence of an established maintenance cycle for a security-focused package.
The repository recorded zero commits and zero active maintainers in the past three months. The package is relatively young, but there is still no recent evidence of ongoing maintenance.
Composer is used for the build, but no security-scanning tools are configured. For an encryption package, that leaves an important quality-control gap.
The repository has no security policy. That reduces transparency about how vulnerabilities should be reported and handled, which matters for a package handling encryption and API requests.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0 | — | — |
phpseclib/phpseclib Version ^3.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.