icanboogie/datetime

Clear documentation, repository tests, and a small dependency surface reduce adoption friction. Maintenance has been quiet for about 16 months, and all six workflow action references are unpinned; the missing security policy adds a smaller transparency concern.

Latest v3.0.0

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed since 2013 with 13 releases, but there were no releases in the 12 months before collection and the latest release was about 16 months earlier. This indicates a mature but currently quiet project.

Repo commit activity

There were no commits and no active maintainers in the three months before collection, consistent with roughly 16 months since the latest release. This lowers confidence in prompt maintenance, though the package remains mature and stable.

Repo tooling

The repository uses Composer and Make for builds, but no security scanning tools were detected. The established build tooling is positive; the missing scanning is a modest hygiene gap.

Security policy

The repository has no security policy. This does not establish a vulnerability, but it reduces transparency about how security issues are reported and handled.

Workflow audit

Both workflows were analyzed successfully and have no detected dangerous sinks or audit findings. However, all six action references are unpinned, leaving workflow behavior exposed to upstream changes.