Package Health/miklcct/rail_open_timetable_data

miklcct/rail_open_timetable_data

This release appears suitable to depend on from a maintenance and transparency perspective: it has a substantial release history, frequent recent releases, a stable non-prerelease version, an active and unarchived source repository, clear MIT licensing, tests, a changelog, and no install-time lifecycle scripts. The main concern is maintenance concentration: all 15 commits in the last 3 months came from one contributor, and the repository has no observable security scanning or security policy. Very low popularity is a supporting weakness but not decisive for a focused open-source library. Overall, the package looks actively maintained but has notable single-maintainer and security-process risk.

Latest 2.4.0

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual user rather than an organization, so the concentrated maintainer activity cannot be discounted as normal organization-level delegation.

Repo bus factor

One contributor made all 15 commits in the last 3 months, creating a genuine single-maintainer continuity risk; the active commit rate partly compensates for the concentration but does not eliminate it.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is not inherently negative, but it provides little evidence of community maintenance or review.

Repo popularity

The repository has zero stars and forks and only one watcher, which provides little external adoption evidence and modestly increases uncertainty, though popularity is not decisive for package health.

Repo tooling

Composer is used as a build tool, supporting reproducible project management, but no security-scanning tools were detected, leaving a security-process gap.