Documentation and licensing are in place, and the repository directly references the package. The absent security policy and scanning reduce transparency for a client handling financial APIs.
62%
Total Score
25
100
88
83
The repository had zero commits and zero active maintainers in the past three months. For a new API client, that provides weak evidence of ongoing compatibility and maintenance.
Only one registry account can publish the package, leaving a thin publishing base. The repository is user-owned rather than organization-backed, so no broader ownership is shown to offset that limitation.
The package is 164 days old but has only one release, so there is little evidence of an established release process or ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected, reducing the project's routine security oversight.
The repository has no security policy, which is a transparency gap for a client handling authentication and financial API operations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
firebase/php-jwt Version ^6.0 | — | — |
guzzlehttp/guzzle Version ^7.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.