try/clear-string

Release historydanger

The latest release was in October 2017, with no releases in the following nearly nine years. That long gap is strong evidence of abandonment risk, although the package may be functionally complete.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and providing no evidence of current maintenance.

Maintainerscaution

Only one registry account can publish releases, which creates a thin operational base. The organization-backed repository partly offsets this, but no recent activity shows that the backing is active.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, so there is little visible community adoption or external support to compensate for the inactive maintenance record.

Repo toolingcaution

The repository uses Composer build tooling, but no security scanning tools were detected. For this small, old utility this is a minor hygiene gap rather than a standalone adoption blocker.