zems/lib_res

Release historydanger

Only one release exists, published about 2 years 10 months ago, with no releases in the last 12 months. This is strong evidence of limited maintenance and raises abandonment risk.

Repo commit activitydanger

The repository recorded no commits and no active maintainers during the last 3 months, consistent with the long release gap. No provided activity signal compensates for this lack of recent work.

Repo popularitycaution

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these figures provide little independent evidence of community adoption or support.

Repo toolingcaution

Composer is used for the build, but the repository has no security-scanning tools. That is a modest hygiene gap rather than evidence that the package is unfit by itself.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, though the package's inactivity is the more important concern.