kode/pays
Clear documentation, tests, licensing, and very recent activity improve confidence in the release. Security-policy coverage is absent, and the workflow references are not pinned, so maintenance and build-reproducibility risks remain.
68%
Total Score
50
100
88
67
Health Score Breakdown
The repository is owned by a user account rather than an organization, so the concentrated contributor activity is not visibly supported by organization-level handoff capacity.
The package has 100 releases in 149 days, with the latest published today, showing active maintenance; the extremely compressed median interval suggests unusually high release churn rather than a deliberate cadence.
One contributor made 100% of the 86 recent commits, creating a high single-person dependency for maintenance and response continuity.
The repository recorded 86 commits in the last three months, showing strong activity, but all came from one active maintainer, leaving little demonstrated redundancy.
Composer build tooling is present, but no security-scanning tool was detected, leaving security-focused maintenance less visible.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Kode Team |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/log Version ^3.0 | — | — |
guzzlehttp/guzzle Version ^7.8 | — | — |
Weekly Downloads
Info
- Last Published
- 4 days ago
- Created
- 5 months ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.