cubecoding/dates

The source includes a real test suite, stable versioning, and a matching organization-backed repository. A single maintainer, no security policy, and very small adoption leave limited evidence of ongoing support.

Latest v1.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The published artifact has no README, which makes library adoption less transparent, but the repository contains tests and uses GitHub releases, providing meaningful project documentation and validation evidence.

Release history

The package has only two releases and none in the last 19 months, indicating a notably slow release cadence. Its stable v1.1 release and non-deprecated status provide some reassurance, but not evidence of active maintenance.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the long gap since the latest release. This is a meaningful maintenance concern, though it does not by itself prove abandonment.

Repo popularity

The repository has two stars, no forks, and no watchers, showing very limited adoption and external validation. Popularity is supporting evidence rather than a decisive health measure.

Repo tooling

Composer is used for the build, but no security scanning tooling is present. The missing scanner is a hygiene gap rather than evidence that the package is unsafe.