A security policy is missing, while issue handling has also been quiet. Organization ownership, regular releases, a clear README, and a license file provide useful support.
72%
Total Score
75
100
94
75
Only one commit was recorded in the last three months, showing a slow recent maintenance pace. This is partly balanced by the package's regular release history, but still lowers confidence in active development.
The repository has 12 open issues, but no new or closed issues and no merged pull requests in the last month. This suggests limited recent issue handling, though it is not evidence of abandonment by itself.
Composer is used for builds, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy. For an SDK handling advertising API credentials and access tokens, the lack of documented vulnerability reporting and handling is a real transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version * | — | — |
guzzlehttp/guzzle Version ^6.2 || ^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.