bugban/codeigniter

This is a young but actively maintained package: it has 12 stable releases over 55 days, recent repository activity, two contributors with evenly split commits, no deprecation, and a clear MIT declaration. Its main risks are limited maturity and transparency: the package and repository contain only five files, no tests or changelog, the repository has no security policy or security scanning, and it has no observable adoption or issue activity. The small adapter scope makes the minimal structure and absent tests less concerning than they would be for a larger library, but the short history means adopters should monitor future releases and validate compatibility in their own CodeIgniter environments.

Latest v1.7.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package file tree

The artifact and repository each contain only five files, including two source files and documentation. This is consistent with a narrowly scoped adapter but leaves little visible project structure for validation.

Package scaffolding

A substantial README documents installation and CodeIgniter 3/4 usage, but both the artifact and repository lack tests and a changelog. For a small framework adapter this is a meaningful, though not severe, maturity gap.

Project backing

The repository is owned by an individual user rather than an organization, so the small maintainer base cannot be treated as organization-backed maintenance capacity.

Release history

The package is only 55 days old but has 12 releases in that period, with a median interval of about 6 hours 36 minutes. This demonstrates active iteration, while the short history limits confidence in long-term stability.

Repo bus factor

Two contributors each account for 9 of the last three months' commits, so activity is not concentrated in one contributor. The total contributor base is still small, limiting resilience if either becomes inactive.