sbkl/laravel-expo-push-notifications

Release historydanger

The package has had no release in nearly six years: its latest release was August 2020, with none in the last 12 months. This is strong evidence of abandonment risk despite the 11-release history.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating that fixes are unlikely to arrive promptly.

Maintainerscaution

Only one account has registry publish access. With no organization backing shown, this leaves the release dependent on a very thin maintainer base.

Project backingcaution

The registry namespace and repository owner are the same individual account, with no organization backing indicated. This supports the thin-maintainer concern rather than compensating for it.

Repo issue activitycaution

There are no open issues or pull requests and no activity in the last month. This is consistent with a dormant project, though it does not show unresolved maintenance work.