Package Health/hollodotme/crontab-expression

hollodotme/crontab-expression

Usable with caveats: the package is transparent and tested, but it has had only one release and no commits for more than five years. Treat it as stable legacy code and verify that its PHP and dependency requirements still fit your project.

Latest v0.1.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Lifecycle scripts

Composer post-install and post-update scripts run during dependency operations. Their presence deserves review because install-time code increases operational exposure, although this signal alone does not show that the scripts are dangerous.

Release history

This is the only release, published about 8 years and 9 months ago, with no releases in the last 12 months. The long absence of releases is a meaningful maintenance concern.

Repo commit activity

There were no commits and no active maintainers in the last three months, indicating the project is currently inactive and increasing abandonment risk.

Repo popularity

The repository has zero stars and forks and only one watcher. This is weak supporting evidence of limited adoption, but popularity alone is not decisive for a small library.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. This is a transparency and assurance gap, not evidence that the package is unsafe.