bart1337/slack-php-api

Release historydanger

Only two releases exist, with the latest published in August 2023 and none in the following three years. That long release gap raises abandonment risk for an API client whose upstream service can change.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the multi-year release gap. This is strong evidence that ongoing maintenance capacity is absent.

Project backingcaution

The repository is owned by an individual account rather than an organization, so the small registry maintainer list has no organizational backing to compensate for the lack of recent activity.

Repo issue activitycaution

There were no new or merged pull requests and no issue activity in the last month. This supports the maintenance concern, although the null open-issues count limits what can be inferred about backlog.

Repo popularitycaution

The repository reports zero stars, forks, and watchers. Popularity is only supporting evidence, but these counters provide no external activity signal to offset the maintenance gap.