Documentation, tests, and release notes support a well-structured library. However, no release or commit activity for over five years and no security policy or scanning leave maintenance and security ownership uncertain.
58%
Total Score
0
75
75
The package has made no release in more than five years, with only three releases overall. That long pause materially raises abandonment and compatibility risk.
The repository recorded no commits and no active maintainers in the last three months, consistent with the package's prolonged release silence.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the absence of community visibility provides little compensating evidence for the stale maintenance record.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces assurance for a library that handles payment API integration.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it does not by itself show a security defect.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.0 | — | — |
lmc/http-constants Version ^1.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.