jpi/cron-linter

The package includes tests, release notes, a license, and a small dependency set, with no install-time scripts. Maintenance is concentrated in one contributor, and the workflow uses both actions without pinning; the missing security policy is a smaller transparency gap.

Latest v2.0.0

Packagist

76%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publish access. Because the repository is owned by an individual rather than an organization, this represents a real continuity risk despite active repository work.

Project backing

The registry namespace and repository are owned by the same individual, so the package has clear ownership but no organizational backing shown by the collected evidence.

Repo bus factor

One contributor made all recorded commits in the last three months, with a 100% share. For this individually owned project, that concentration creates a meaningful continuity risk.

Repo issue activity

There is one open issue and one open pull request, with no issues or pull requests opened or closed in the last month. This is a mild indication of limited community activity, not abandonment by itself.

Repo popularity

The repository reports zero stars, forks, and watchers. This is weak supporting evidence and lowers confidence in community resilience, but it does not outweigh the observed maintenance activity.