ad3n/cron

The source includes a clear README, changelog, tests, matching package references, and an MIT license. Workflow analysis found complete coverage and no dangerous findings, but there is no security policy and all four action references are unpinned.

Latest v1.0.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The package and repository are both owned by the same individual account, so the source appears aligned with the package. Individual ownership also means the project has no demonstrated organizational backing to offset its thin maintenance evidence.

Release history

The package has only one release, published about 20 months ago, with no releases in the last 12 months. This leaves maintenance continuity unproven and lowers confidence in long-term support.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the single release, this is meaningful evidence of weak current maintenance.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is supporting evidence rather than a verdict, but this provides no external indication of adoption or community support.

Repo tooling

Composer build tooling is present, but no security-scanning tooling was detected. The missing scanner is a modest transparency and hygiene gap, not evidence of unsafe code.