The package is small, clearly licensed, and backed by an organization, but it has little visible maintenance or security process. Its narrow scope may explain the limited history, yet the long period without updates makes adoption a liability for new projects.
42%
Total Score
50
69
50
The last release was published nearly five years ago, with only two releases ever and none in the past 12 months. This is strong evidence of abandonment risk, though the package may be intentionally stable.
There were no commits and no active maintainers during the past three months, consistent with a project that has stopped receiving maintenance. The organization-owned repository offers some backing but no observed recent work.
Composer build tooling is present, but no security scanning tooling was detected. This is a modest transparency and maintenance gap, especially for a package handling an API token.
The repository is not archived, which preserves a path for future maintenance. However, its last push was nearly five years ago, so this does not offset the inactivity evidence.
The repository has no security policy, leaving vulnerability reporting expectations unclear. This is a process gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
php-http/guzzle6-adapter Version ^1.0 | — | — |
m4tthumphrey/php-gitlab-api Version ^9.18 | — | — |
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.