appsco/component-assertion-voter

Release historydanger

The package has only one release, dated May 6, 2014, with none in the last 12 months. This is strong evidence of an unmaintained release and materially raises abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Given that the last push was in 2014, maintenance has effectively collapsed, creating a major abandonment concern.

Project backingcaution

The source repository is owned by an organization, which provides some backing context and makes a short registry maintainer list less concerning. It does not demonstrate current stewardship because the repository has been inactive since 2014.

Repo issue activitycaution

There are no open issues or pull requests and no issue or pull-request activity in the last month. While a quiet issue tracker is not inherently bad, here it is consistent with the decade-long inactivity.

Repo package mentioncaution

The repository name does not match the package name, and its README does not mention the package. This raises concern that the linked repository may not clearly belong to this release, weakening provenance transparency.