It has a README, tests, and matching MIT licensing, which make the small codebase easier to inspect. The repository has no security scanning or security policy, adding transparency concerns.
42%
Total Score
100
100
71
75
The package has only one release, published over seven years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.
Composer build tooling is present, but no security scanning tools were detected. For a library handling bank API integration and encryption, this is a meaningful maintenance and transparency gap.
The repository has no security policy. That weakens the project's disclosure and maintenance process, especially for a package dealing with financial API integration.
The latest version is v0.1 and is not a stable major release, so compatibility and long-term API support remain uncertain. The absence of prerelease labeling does not offset the very early version.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.3.3 | — | — |
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.