ppeerit/time

Maintainerscaution

Only one registry account has publishing access. The repository is user-owned rather than organization-backed, so there is little visible redundancy if that maintainer stops responding.

Project backingcaution

The registry namespace and repository are tied to individual accounts, with the repository owner identified as a user. This provides no organizational backing to compensate for the single-maintainer profile.

Release historycaution

The package has only 3 releases, all clustered on April 9, 2017, with no releases in the last 12 months and a package age of about 9 years. This is strong evidence of abandonment risk.

Repo commit activitycaution

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap. No newer development activity compensates for this maintenance concern.

Repo issue activitycaution

There are no open issues or pull requests and no recent issue or pull-request activity. While a clean tracker can be positive, here it does not compensate for the broader absence of project activity.