The package includes tests, a usable file layout, and an MIT declaration. Organization backing and no install-time scripts help, but the project has limited evidence of sustained maintenance or package identity.
58%
Total Score
75
100
71
75
There has been only one release, published about 10 months ago, so there is little evidence of an established release process. The repository is still available and not archived, which partly offsets the maturity concern.
The repository had zero commits and zero active maintainers in the last three months, despite being created or released about 10 months ago. The single release and organization ownership do not compensate for the absence of recent observed work.
The repository name does not match the package name and its README does not mention the package, so the link between the published package and source repository is not clearly established. Organization backing and matching namespace reduce, but do not remove, that concern.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The package is an SDK with network-related dependencies, so this gap is relevant.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nesbot/carbon Version ^3.10 | — | — |
league/flysystem Version ^3.0 | — | — |
vlucas/phpdotenv Version ^5.4 | — | — |
guzzlehttp/guzzle Version ^7.3 | — | — |
symfony/serializer Version ^6.2 | — | — |
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.