amir-hossein5/laravel-ip-logger

Release historydanger

Only three releases exist, with the latest published over four years ago and no releases in the last 12 months. This is strong evidence of an unmaintained package.

Repo commit activitydanger

The repository has zero commits and zero active maintainers in the last three months, following a last push over four years ago. This materially raises abandonment risk.

Maintainerscaution

Only one registry account can publish releases. The matching user-owned repository provides ownership continuity, but the single-person publishing base increases continuity risk.

Project backingcaution

The package and repository are owned by the same individual account, so the source link is consistent; however, this is individual rather than organizational backing.

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 is weaker evidence than the long-term release and commit gaps.