gumphp/think-crontab

Release historydanger

Only two releases were published, both about three years ago, with no release in the last 12 months. That is strong evidence of an inactive project, though not proof it is unusable.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.

Repo toolingcaution

Composer build tooling is present, but the repository has no security scanning tools. This weakens ongoing supply-chain oversight for a package intended to run in applications.

Security policycaution

No security policy is provided, leaving no documented process for reporting or handling vulnerabilities. The small package scope partly limits the significance of this gap, but does not remove it.