marcossantos/mailbit-library-laravel

Release historydanger

The latest release was over two years ago, with no releases in the last 12 months and only four releases overall. This is strong evidence of stalled maintenance for a package intended to provide an API integration.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating a serious abandonment risk.

Package scaffoldingcaution

A readme and changelog are present, but the readme describes Guzzle rather than this Mailbit Laravel package. The absence of packaged tests is normal for a published PHP artifact, while the misleading documentation is a transparency concern.

Project backingcaution

The repository is owned by an individual account rather than an organization, so there is no provided evidence of organizational backing to compensate for the single-maintainer profile.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap for a package handling API communication.