tzookb/tbmsg

Release historydanger

The package has made no releases in the last 12 months, and its latest release was in February 2016 despite 19 releases overall. This long release gap materially raises abandonment risk.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Together with the old latest release, this is strong evidence that maintenance has effectively stopped.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, with six issues and one pull request still open. This supports a caution about inactive project follow-through.

Repo toolingcaution

The repository uses Composer, but no security scanning tools were detected. That is a modest transparency and maintenance gap, not a standalone adoption blocker.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds a maintenance concern for a package handling user messaging data.