Tests, a clear MIT license, and organization ownership provide useful transparency. The missing security policy and minimal repository adoption add concern, so this release warrants caution for new dependencies.
40%
Total Score
50
71
75
The latest release was nearly eight years ago, with only two releases overall and none in the last 12 months. This strongly suggests the package is no longer actively maintained.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.
The repository has zero stars, one fork, and one watcher, providing little supporting evidence of adoption or community oversight. Popularity is supporting evidence, so this is a moderate concern rather than a decisive failure.
Composer build tooling is present, but no security scanning tools were detected. The tooling supports normal packaging, while the missing scanning is a minor hygiene gap.
No repository security policy was found, reducing transparency about vulnerability reporting and response. This matters more for a database integration package, though it is not severe on its own.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
carno-php/dsn Version ^1.0 | — | — |
carno-php/net Version ^1.0 | — | — |
carno-php/pool Version ^1.0 | — | — |
carno-php/cluster Version ^1.0 | — | — |
carno-php/promise 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.