illchuk/zfc-user-substitute

Release historydanger

Only two releases were published, both in September 2017, with no release in roughly nine years. This is strong evidence of abandonment for a dependency that may need compatibility or security updates.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in September 2017. The long inactivity materially raises maintenance risk.

Maintainerscaution

Registry publishing is controlled by one user account, with no organizational backing shown. A single maintainer is not inherently unhealthy, but combined with the long inactivity it leaves little visible maintenance capacity.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. Although this can occur with subpackages, the mismatch reduces confidence that the source repository clearly documents this release.

Security policycaution

The repository has no security policy. For a package that changes user identity or access behavior, the absence of a stated vulnerability-reporting process is a meaningful transparency gap.