m1guelpf/integration

Release historydanger

The package has had only two releases, with the latest published in February 2018 and none in the last 12 months. This is strong evidence of abandonment for a library that may need compatibility and security maintenance.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the last release being over eight years ago, this indicates a substantial abandonment risk.

Dependency profilecaution

Five runtime dependencies, including a GitHub API client, JWT library, HTTP adapter, and Laravel support, create meaningful maintenance and compatibility exposure for an old package. The dependency count is not excessive, but these integrations increase the cost of remaining current.

Project backingcaution

The repository is owned by an individual user rather than an organization, and no broader project backing is shown. That makes the inactive maintainer base more consequential for continuity.

Repo issue activitycaution

There have been no new issues or merged pull requests in the last month, with one pull request still open. This is consistent with a largely inactive project, though it is weaker evidence than the release and commit history.