Documentation, tests, and release notes make integration clearer. However, the package is brand new, all recent commits come from one maintainer, and its two workflow actions are unpinned, so long-term continuity and build reproducibility remain uncertain.
68%
Total Score
67
100
88
67
The repository is owned by the same individual namespace that publishes the package, so ownership is consistent but lacks organizational backing.
The package has only two releases, both within the same day, so there is not yet enough history to demonstrate durable maintenance. The rapid initial release activity is mildly reassuring but does not offset the lack of track record.
One contributor made all 10 recent commits, leaving the project dependent on a single active maintainer. Because the repository is user-owned rather than organization-backed, this is a meaningful continuity concern.
Composer build tooling is present, but no security scanning tooling is configured. That is a modest repository-hygiene gap rather than evidence of unsafe code.
The repository has no security policy, which leaves vulnerability reporting and response expectations unclear for a package that handles API authentication.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^2.0 | — | — |
christianjbrown/api-client Version ^1.0 | — | — |
symfony/dependency-injection Version ^8.0 | — | — |
christianjbrown/oauth2-client Version ^1.0 | — | — |
christianjbrown/key-value-store Version ^1.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.