philo/laravel-twitter

Release historydanger

The package has only two releases, both from February 2015, with no releases in the last 12 months. This long publication gap is strong evidence of abandonment risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push in February 2015. This materially increases the risk that defects and compatibility changes will go unaddressed.

Dependency profilecaution

The package has three runtime dependencies and no development dependencies. The count is modest, though its old Laravel 4 and TwitterOAuth integration may limit compatibility with current projects.

Maintainerscaution

The registry lists one maintainer. This is not inherently unhealthy, but there is no organizational backing or recent activity signal showing continued maintenance capacity.

Project backingcaution

The repository is owned by an individual account rather than an organization, so there is no demonstrated organizational backing to compensate for the single-person project context.