kepler/gigachat

The package has only one release and one contributor, with no tests or security policy. Its MIT declaration, recent repository activity, minimal dependency set, and package-specific README provide some support, but the project remains lightly established.

Latest v1.0.0

Packagist

58%

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 the bundle, configuration, README, and manifest. This is consistent with a small integration but provides little evidence of broader project maturity.

Package scaffolding

A README is present, which helps consumers, but the package and repository contain no tests or changelog; the missing tests are a meaningful maturity gap for a library.

Project backing

The repository owner is an individual user rather than an organization, so there is no visible organizational backing to offset the small maintainer base.

Release history

There has been only one release, published 93 days ago, so there is not enough release history to demonstrate sustained maintenance.

Repo bus factor

All recent commits come from one contributor, leaving maintenance dependent on a single person. The repository owner is an individual, so no organizational handoff evidence compensates for that concentration.