evelution87/file-input

Release historydanger

The latest release was published nearly four years ago, with no releases in the last 12 months. Fourteen releases were clustered within about one day, showing no continuing release cadence.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the nearly four-year release gap and indicating severe abandonment risk.

Maintainerscaution

One registry account has publish access. The linked repository is user-owned rather than organization-owned, so the narrow publishing base provides little redundancy, especially alongside inactive development.

Package scaffoldingcaution

A README and changelog are present, but the README is largely unfilled boilerplate with placeholder usage guidance. No tests are published or present in the repository, which is normal packaging practice and not itself a gap.

Project backingcaution

The registry namespace and repository are owned by the same individual account, with no organization backing shown. That is consistent ownership but offers limited maintenance redundancy.