gxz/sm3

Release historydanger

There has been only one release, published about 6 years ago, with none in the last 12 months. This is strong evidence of abandonment risk despite the stable 1.0 version.

Repo commit activitydanger

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

Maintainerscaution

Only one registry account has publish access. For this user-owned project, that represents a thin publishing and maintenance base rather than organization-backed capacity.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds a transparency concern for a cryptography package.