eduardoavargas/laravel-pipefy

Release historydanger

There has been only one release, published about 7 years and 7 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and materially increasing abandonment risk.

Dependency profilecaution

The package has seven runtime requirements, including standard Laravel, Guzzle, and PHP dependencies. The dependency count is not excessive, though no development dependencies provide little evidence of a maintained test setup.

Maintainerscaution

Only one registry maintainer is listed. For a user-owned project this is plausible, but it leaves limited observable publishing continuity if that maintainer stops working on it.

Package file treecaution

The complete package and repository tree contains only 9 files, consisting mainly of source and configuration files; this provides little evidence of mature project practices.