yanivgal/cronom

Its MIT licensing and small runtime dependency set are straightforward. No commits or releases have appeared since April 2016, and the repository has no security policy, leaving maintenance and security support uncertain.

Latest 1.0.5

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in more than 10 years: its latest release was April 17, 2016, despite six total releases. This is strong evidence of abandonment for a dependency that may need ongoing compatibility fixes.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since April 2016. The non-archived status does not compensate for the absence of observed maintenance.

Package scaffolding

The package includes a README, but it is only 26 characters long and provides minimal consumer guidance. The absence of tests and a changelog is normal for a published artifact and is not counted against the release.

Repo popularity

The repository has zero stars, forks, and watchers, providing no supporting evidence of a broader community that might help sustain or review the package. Popularity is only supporting evidence, but its absence adds to the maintenance concern here.

Security policy

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This compounds the risk of relying on a project with no recent maintenance.