thirty-two

Maintainerscaution

Only one account has registry publish access, leaving little visible publishing redundancy. The linked repository is owned by the same individual, so this is a genuine thin-maintainer concern rather than an organization-backed project.

Release historycaution

The latest release was in July 2016, with no releases in the last 12 months and a long median release interval. This strongly lowers confidence in current maintenance, although the package may be stable if its narrow functionality is unchanged.

Repo commit activitycaution

The repository had zero commits and zero active maintainers in the last three months. A push in May 2023 shows it is not archived, but current development activity remains absent.

Security policycaution

The repository has no security policy. This is a transparency and maintenance gap, though the small, stable package has no other provided security-process evidence to offset it.