martinezdelariva/railway

Usable with caveats: it has clear licensing, documentation, tests, and a small dependency surface, but the only release was about nine years ago and repository activity stopped about five years ago. Treat it as a stable legacy package rather than an actively maintained dependency.

Latest v1.0

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with repository activity having stopped about five years ago. This is the main abandonment concern.

Maintainers

Only one registry maintainer is listed. That is a limited individual maintainer base, and the project backing signal identifies a user-owned rather than organization-owned repository.

Project backing

The registry namespace and repository owner match, but both identify an individual account rather than an organization. This supports ownership continuity without providing organizational maintenance capacity.

Release history

The package has only one release, published about nine years ago, with no releases in the last 12 months. That substantially lowers confidence in ongoing maintenance, although a small stable library can still remain usable.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. The lack of scanning is a transparency gap, though it is less severe for this small, inactive package than evidence of unsafe workflows would be.