The package has clear documentation, tests, an MIT license, and a recent release. Its small audience, absent security policy and scanning, and reliance on one recent contributor leave maintenance continuity uncertain.
68%
Total Score
67
100
89
50
One contributor made all two commits in the last three months, giving the project a 100% recent commit share for one person. Organization ownership provides some handoff capacity, but no second active contributor is shown.
The repository recorded two commits in the last three months, showing recent activity but a low level of ongoing development. This supports maintenance at a modest level rather than indicating a highly active project.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counts provide no external adoption or community-maintenance cushion.
Composer build tooling is present, but no security-scanning tools were detected. The build is structured, while automated security coverage is not evident.
The repository has no security policy, leaving no documented process for reporting and handling vulnerabilities. This is a transparency and maintenance gap for an API integration library.
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.