Usable with caveats: this is a newly published v1.0.0 with no demonstrated maintenance history yet. The small five-file repository has clear licensing and documentation, but no tests, security policy, or commit activity beyond its initial publication.
62%
Total Score
50
100
89
88
The registry namespace and repository owner match the same individual account, providing direct ownership alignment. There is no organizational backing signal, so long-term continuity depends on one apparent owner.
The package was released once and is 0 days old, so there is no track record for maintenance, compatibility, or release reliability. This is an uncertainty for adoption, though it is expected for a brand-new package rather than evidence of abandonment.
There were zero commits and zero active maintainers in the last three months beyond the initial publication. Because the package is only 0 days old, this mainly reflects missing history, but it leaves maintenance capacity unproven.
The repository uses Composer, but no security scanning tools are configured. The build setup is appropriate, while the missing scanning is a modest transparency and maintenance gap.
No security policy was found in the repository. For an SDK handling authentication, tokens, and user data, the absence of a stated vulnerability-reporting process is a meaningful transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.8 | — | — |
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.