frowhy/jpush

Release historydanger

The last release was in September 2017, about 9 years ago, with no releases in the past 12 months. Four releases show an established package, but the long gap is a serious maintenance concern.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past 3 months, consistent with the release gap and indicating that maintenance has effectively stopped.

Package scaffoldingcaution

The published artifact has no README, which makes a Laravel integration harder to adopt and understand. Missing tests and a changelog are normal for published artifacts and are not counted against it.

Repo popularitycaution

The repository has 1 star and 1 fork, providing little supporting evidence of broad community review or outside maintenance. Low popularity alone is not decisive, but it offers no meaningful counterweight to the inactivity.

Repo toolingcaution

Composer is used for the build, but the repository reports no security scanning tools. This is a hygiene gap that adds uncertainty for a dependency with no recent maintenance evidence.