o-ba/covid-php

The package is clearly documented, licensed, and tied to a matching source repository, with release notes recording a dependency security update. Its small single-person project has no recent development activity or security policy, so future compatibility and maintenance are uncertain.

Latest 1.2.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in more than four years, with zero releases in the last 12 months; its earlier median interval of about 28 days shows this is a sustained stoppage rather than an established slow cadence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release gap and indicating no current maintenance capacity.

Maintainers

Only one registry account can publish the package, creating a thin publishing base for a user-owned project and increasing continuity risk if that maintainer becomes unavailable.

Repo tooling

Composer build tooling is present, but no security-scanning tooling was detected. That is a modest hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a transparency gap, though the release notes do document a prior Guzzle security update.