hameleon2x/llm-orchestra

This is a young but actively maintained package with 11 releases over 103 days, a recent push, 21 commits in the last 3 months, clear licensing, substantial documentation, a matching repository, and no install-time scripts or deprecation status. The main adoption risks are that the project is still pre-1.0, all recent commits come from one maintainer, the repository has no observed community activity or popularity, and no security policy or automated security scanning was found. Repository tests compensate for the absence of packaged tests, so the package is usable but should be adopted with normal caution and awareness of its immature, single-maintainer profile.

Latest v0.4.2

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account, Hameleon2x, has publish access. This is a real continuity risk for a user-owned project, although repository activity shows that the maintainer is currently active.

Project backing

The repository is owned by a user account rather than an organization, so maintenance continuity depends primarily on one individual. This reinforces the single-maintainer concern but does not indicate abandonment while recent commits remain active.

Release history

The package is only 103 days old but has 11 releases, all within the last 12 months, with a median interval of about 2 days. This demonstrates active iteration but not yet long-term maturity.

Repo bus factor

All 21 recent commits were made by one contributor, giving the project a bus factor of one. Because the backing owner is a user rather than an organization, there is no provided organizational handoff evidence to offset this concentration.

Repo issue activity

There are no open issues or pull requests and no issue or PR activity in the last month. The clean queue is not inherently negative, but the absence of community interaction limits evidence of external review and support.