Clear documentation, tests, and release notes make the client easier to adopt and maintain. Add extra scrutiny because security scanning is absent and the workflow uses two unpinned actions.
68%
Total Score
70
100
88
75
Only one registry account has publish access. This is consistent with the matching user-owned repository but leaves release continuity dependent on one person.
The registry namespace and repository belong to the same individual, providing consistent ownership but no organizational backing to offset the single-maintainer risk.
The package was first released today and has only two releases, so there is not yet enough history to establish reliability or long-term maintenance.
One contributor made all 21 recent commits, so maintenance has a low bus factor and could be disrupted if that contributor becomes unavailable.
Composer build tooling is present, but no security-scanning tooling was detected, leaving an avoidable supply-chain hygiene gap.
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.