carno-php/devops

The package is clearly licensed and tied to a matching organization repository. Its minimal three-file footprint and lack of security scanning leave little evidence of development or operational safeguards.

Latest 1.0.0

Packagist

39%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Package file tree

Both the artifact and repository contain only three files: LICENSE, README.md, and composer.json. For a library described as providing multiple operational components, this unusually small footprint provides little transparency into implementation or maintenance.

Release history

This is the package's only release, published about 7 years and 10 months ago, with no releases in the last 12 months. That strongly raises abandonment risk, although the package is not marked deprecated.

Repo commit activity

The repository recorded no commits and no active maintainers in the last 3 months, consistent with the long release gap and indicating no recent maintenance capacity.

Repo tooling

Composer is used for the build, but the repository reports no security-scanning tools. This is a modest transparency and maintenance gap, especially for a package handling logging, metrics, tracing, and network integrations.

Security policy

The repository has no security policy, so consumers have no documented process for reporting vulnerabilities or understanding security maintenance expectations.