m-jch/date

Release historydanger

The package has had no release in over 7 years, with zero releases in the last 12 months. Its five-release history shows it was once maintained, but this does not offset the prolonged inactivity.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the last push occurring over 7 years ago. This is strong evidence of abandonment risk.

Maintainerscaution

Only one registry maintainer is listed, which limits visible publishing redundancy for a user-owned project. The repository's matching owner provides some continuity but does not remove the single-maintainer risk.

Security policycaution

The repository has no security policy, leaving no documented path for reporting vulnerabilities. This is a transparency and maintenance gap, though it is less severe than the prolonged inactivity.