The repository has no security policy, no security scanning, and both workflow actions are unpinned. A substantial README, tests, release notes, and recent activity provide useful transparency, but the project is too new to establish a long maintenance record.
68%
Total Score
63
100
81
67
The repository is owned by an individual user, so there is no organization backing to offset the concentrated maintainer base or provide an evident handoff path.
The package is 0 days old with only 2 releases, so its maintenance record and maturity are not yet established. This is a meaningful caution for a library dependency, though recent publication activity shows the project is active now.
One contributor made 100% of the recent commits. Because the project backing is an individual account rather than an organization, this concentration is a real continuity risk.
There were 14 commits in the last 3 months, all from one active maintainer. The recent activity is positive, but the single-contributor base leaves limited evidence of durable maintenance capacity.
The repository has 0 stars, forks, and watchers. For a package released on the assessment date, this is weak supporting evidence but not by itself evidence of poor health.
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.