combell/combell-api

Release historycaution

The package is nearly 10 years old but has only 6 releases, with a median interval of about 15 months and one release in the last year. The recent v4.0 release shows activity, but the long cadence limits maintenance visibility.

Repo bus factorcaution

All 2 recent commits came from one contributor, creating concentrated maintenance responsibility. Organization ownership provides some handoff capacity, but no second active contributor is shown.

Repo commit activitycaution

There were only 2 commits in the last 3 months, so recent maintenance is light even though the repository was updated for this release.

Repo toolingcaution

Composer and Phing provide build tooling, but no security scanning tool is present. That is a transparency and maintenance-process gap rather than evidence of unsafe code.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a moderate transparency gap for a client handling API credentials.