aliqasemzadeh/zibalfacilities

Maintainerscaution

Registry publishing access is held by one person. Because the repository is user-owned rather than organization-backed, this indicates a thin maintainer base and limited continuity if that maintainer stops working on it.

Project backingcaution

The registry namespace and repository owner match, and the owner is an individual user. This confirms direct ownership but provides less organizational continuity than a backed project.

Release historycaution

The package published seven releases in a short initial burst, but has had no release in nearly two years and none in the last 12 months. This is meaningful abandonment risk despite the earlier release activity.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the long release gap, this materially raises abandonment risk.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap, not a severe risk by itself.