cshaptx4869/http-crontab

The project has had no commits or releases for more than three years, and its single-maintainer structure offers limited visible maintenance capacity. A substantial README, declared Apache-2.0 license, stable version, and no install scripts provide useful safeguards, but the lack of tests and security tooling leaves weaker ongoing assurance.

Latest v2.0.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months, indicating no observed current development activity.

Dependency profile

Six runtime requirements, including Workerman, MySQL support, and a routing library, create a moderate dependency surface for a service package. The profile is understandable but increases the number of components that must remain compatible.

Project backing

The package and repository are owned by the same individual account, providing clear ownership but no organization backing or broader institutional maintenance capacity.

Release history

The package has only three releases, with the latest published more than three years ago and no releases in the last 12 months. This is meaningful evidence of limited ongoing maintenance for a service library.

Repo tooling

Composer is used for builds, providing basic project tooling, but no security scanning tools are configured. That is a modest transparency and assurance gap rather than a severe risk by itself.