nikba/laravel-bussystem-api

Maintainerscaution

Only one account has registry publish access. This is a meaningful resilience concern because a single publisher provides little demonstrated continuity if that person becomes unavailable.

Project backingcaution

The repository is owned by a GitHub user rather than an organization, so the single-maintainer and limited-backing concerns are not mitigated by organization ownership evidence.

Release historycaution

Only two releases exist across approximately 437 days, with one release in the last 12 months and a median interval of about 437 days. This limited release history weakens evidence of sustained maintenance.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers during the last three months, which is the strongest maintenance concern in the collected evidence. The very recent push shown by repository_archived partially offsets this, but does not demonstrate sustained activity.

Repo issue activitycaution

There are no open issues or pull requests and no activity in the last month. This is not inherently unhealthy for a small package, but it also supplies no evidence of an active maintenance or user-feedback loop.