showapp/laravel-chargebee

Release historydanger

Only two releases were published, both around March 2020, with no releases in the last 12 months. That long release gap raises abandonment and compatibility risk.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old release history, this is a meaningful maintenance concern.

Project backingcaution

The linked repository is owned by a user account rather than an organization. This does not establish strong institutional backing, but it is not itself evidence of abandonment.

Repo popularitycaution

The repository has zero stars and one fork, offering little supporting evidence of broad community adoption. Popularity is only supporting evidence, so this weighs lightly.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured, leaving a security-hygiene gap for a package handling billing integrations.