readline

Build provenancecaution

No build attestation, trusted publisher, or staged publishing is reported. This weakens release transparency, though it is a provenance gap rather than a direct health verdict.

Maintainerscaution

Only one registry account has publish access. Because the repository is individually owned, this is not unexpected, but it leaves a thin publishing and continuity base.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no organizational backing shown to provide additional maintenance capacity.

Release historycaution

The package has 14 releases since 2013, but its latest registry release was on December 28, 2015, with no releases in the last 12 months. This long release gap lowers confidence that new compatibility or defect issues will be addressed.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last three months. Together with the old published release, this is the main maintenance risk, although the repository was pushed in March 2025.