totalist

Maintainerscaution

Only one registry publishing account is listed. That is a modest bus-factor concern for continued releases, with no organizational backing shown to compensate for it.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no observed organizational backing to offset the thin maintainer base.

Release historycaution

The latest release was about three years ago, with no releases in the preceding 12 months. This is a meaningful maintenance concern, although the package is small and the current release may be stable.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers over the last three months, consistent with the long release gap. For a tiny stable utility this may reflect completion, but it still raises abandonment risk.

Repo toolingcaution

The repository uses npm scripts for builds but has no security scanning tools. The missing scanning is a hygiene gap, not a severe dependency-health issue by itself.