at_server/sign

Release historydanger

This package has only one release, published in October 2018, and none in the last 12 months. That long period without releases is strong evidence of abandonment risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the repository having stopped changing years ago. This materially increases abandonment risk.

Maintainerscaution

Only one registry account has publish access. That is a limited publishing base, and the repository is owned by an individual rather than an organization, so there is little visible redundancy if the maintainer stops work.

Project backingcaution

The repository is owned by an individual user, not an organization, and the package namespace does not show broader project backing. Combined with the single maintainer, this offers little visible continuity protection.

Repo toolingcaution

The repository uses Composer, providing basic build tooling, but no security scanning tools were detected. This is a modest transparency and maintenance weakness rather than a standalone adoption blocker.