obokaman/dateranger

The MIT license, included tests, and small dependency footprint make the package straightforward to evaluate and integrate. Ongoing security oversight is limited, with no security policy or scanning evidence.

Latest 1.2.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was over six years ago, with no releases in the past 12 months. That long gap is strong evidence of abandonment risk despite a history of 12 releases.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the release gap and indicating no visible ongoing maintenance.

Repo popularity

The repository has zero stars and forks and only two watchers. Popularity is supporting evidence rather than a verdict, but these counts provide little evidence of a broad active user or contributor base.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning evidence modestly lowers confidence in ongoing project hygiene.

Security policy

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a meaningful transparency gap, though it is less severe than the maintenance inactivity.