kode/scheduling

Project backingcaution

The source repository is owned by a user account, not an organization, so the single-contributor concentration is not visibly offset by broader project backing.

Release historycaution

The package is only 64 days old, but it has 11 releases in that period, including a release within minutes of collection. This shows active iteration but provides little long-term maintenance history.

Repo bus factorcaution

All 9 recent commits came from one contributor, leaving maintenance dependent on a single active person. The repository owner is a user account rather than an organization, so no organizational handoff is evident.

Repo popularitycaution

The repository has zero stars, forks, and watchers. For a 64-day-old package this is weak supporting evidence rather than a standalone failure, but it provides no external adoption signal.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence of unsafe code by itself.