pankaj-ag/larave-mobile-mobile-api

Release historydanger

Only two releases exist, with none in the last 12 months; the latest release is over seven years old. This is strong evidence of abandonment risk despite the regular roughly four-week interval between the original releases.

Repo package mentiondanger

The repository name does not match the package name and its README does not mention the package. That raises uncertainty about whether the linked repository actually owns this package, despite the organization ownership shown separately.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. This indicates a currently inactive development project, though the repository's February 2025 push partially offsets the concern.

Repo popularitycaution

The repository has one star, one fork, and no watchers. This is weak supporting evidence of adoption, but popularity alone does not determine health.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem. No security scanning is configured, a modest hygiene gap rather than a standalone dependency risk.