The repository license conflicts with the package's proprietary declaration, and there is no security policy or automated security scanning. A README, tests, organization backing, and a matching repository provide useful transparency, but do not offset the long maintenance gap.
38%
Total Score
50
100
71
75
The latest release was published about nine years ago, with no releases in the last 12 months. This is strong evidence that the package is no longer actively maintained.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the release history's prolonged inactivity.
The package declares a proprietary license, while the repository contains a GPL-3.0 license file. The mismatch creates legal uncertainty for consumers.
Composer build tooling is present, but no security-scanning tools are configured. That weakens assurance for a package with no recent maintenance activity.
The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for an SDK handling API credentials.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
myclabs/php-enum Version ^1.5 | — | — |
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.