coredump/jdd-api

Release historydanger

The latest release was in May 2021, over five years ago, and there were no releases in the last 12 months. This is strong evidence of abandonment risk despite the package not being deprecated.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the multi-year gap since the last release and indicating a substantial abandonment risk.

Maintainerscaution

Only one account has registry publish access, leaving limited visible publishing capacity. This is a caution rather than a verdict because registry access does not prove the full project contributor base.

Project backingcaution

The source repository is owned by an individual account rather than an organization, and no broader project backing is shown. Combined with the small audience and inactive commits, this limits visible maintenance capacity.

Repo issue activitycaution

There are six open pull requests but no new or merged pull requests in the last month, suggesting outstanding work is not being actively processed.