silverstripe/crontask

Clear licensing, repository tests, release notes, and organization backing support adoption. The workflows use unpinned actions; pin them before relying on automated releases.

Latest 4.0.0

Packagist

64%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 42 releases over roughly 12 years, but no registry release in the last 12 months despite a previously regular cadence. This is a meaningful maintenance concern, though the latest release is documented and the repository remains active enough to be credible.

Repo commit activity

There were no commits and no active maintainers in the three months measured. This supports the release-history concern and lowers confidence in near-term maintenance.

Repo issue activity

There were no new or closed issues or pull requests in the last month, although only two issues and one pull request are open. This is a modest sign of limited current activity rather than a severe concern.

Repo tooling

The project uses Composer build tooling, but no security scanning tools were detected. That is a transparency and hygiene gap, partially offset by the repository's tests and CI workflows.

Security policy

The repository has no security policy. This weakens vulnerability-reporting transparency, but it does not by itself show that the package is unsafe to depend on.