The package includes a substantial README, tests, release notes, and a source repository that clearly matches its name. The license declaration conflicts with the detected license file, and the repository has no security policy.
43%
Total Score
0
75
50
The repository recorded zero commits and zero active maintainers in the last three months, consistent with maintenance having stopped after the 2022 release. This materially increases abandonment risk.
The release declares MIT, while the detected LICENSE file identifies Apache-2.0. A license is present, but the mismatch creates avoidable legal uncertainty for adopters.
The package has only three releases, all concentrated in October 2022, with no releases in the last 12 months. This is a substantial maintenance concern for a library integration, despite its stable versioning.
Composer is used for the build, but no security scanning tool is configured. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This adds a modest transparency concern for an SDK handling advertising API credentials.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.