aws-sign2

Release historydanger

The latest release was published in April 2017, over nine years after the package began, with no releases in the last 12 months. This is strong evidence of abandonment risk, despite the package not being deprecated.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, while its last push was in June 2020. The long absence of development materially lowers confidence in ongoing maintenance.

Maintainerscaution

Only one registry account has publish access. The organization-owned repository makes a short registry maintainer list unsurprising, but it still leaves limited visible publishing redundancy when combined with the lack of recent activity.

Repo issue activitycaution

There was no new or closed issue or pull request activity in the last month, with one issue and one pull request still open. This supports the conclusion that maintenance is currently inactive.

Repo package mentioncaution

The linked repository name does not match the package name and its README does not mention the package. Although name differences can be normal for subpackages, the lack of any README reference makes the repository-package relationship less transparent.