Documentation is thorough, licensing is explicit, and installation has no lifecycle scripts. Repository tooling is limited, with no security policy or scanning, so operational trust depends on the organization’s continuing attention.
72%
Total Score
75
100
88
83
All 3 recent commits came from one contributor, giving the project a fragile individual maintenance base. Organization ownership provides some handoff capacity but no second recently active contributor is shown.
The repository had 3 commits in the last 3 months, so it is active, but the volume is modest for a package receiving frequent releases.
Composer is used for builds, but no security-scanning tools are detected. That leaves a meaningful verification gap for a package intended to run inside applications.
The repository has no security policy, making vulnerability reporting and response expectations less transparent.
The release is not a prerelease, but it remains on the unstable 0.x major line, so compatibility expectations are more limited than for a stable-major package.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
kompo/kompo Version * | — | — |
condoedge/utils Version ^0.2.12 | — | — |
laravel/framework Version >=5.6.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.