mustang-framework/core

Release historydanger

The package has only one release, with no releases in the last 12 months, and the latest release is about three years and six months old. This is strong evidence of abandonment risk, although the repository remains available.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since its last push. This materially increases the risk that bugs and compatibility issues will not be addressed.

Dependency profilecaution

Ten runtime dependencies, including Laravel, Passport, Guzzle, and related framework packages, create a substantial compatibility surface for a package whose release history is inactive. The dependency count is not inherently unsafe, but it increases the cost of adopting an apparently unmaintained release.

Repo popularitycaution

The repository has only 2 stars, 1 fork, and 1 watcher, indicating a small user and contributor footprint. Popularity is supporting evidence rather than decisive, but it offers little reassurance alongside the inactivity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected. The missing scanning is a transparency and maintenance gap, though it is less significant than the lack of release and commit activity.