fknoedt/db-journal

Release historydanger

The package has only one release, 0.3.0, published about 6 years and 10 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last 3 months. Together with the one-release history, this points to weak ongoing maintenance.

Maintainerscaution

The registry lists one maintainer. This is a limited bus factor for a user-backed project and adds some continuity risk, though registry access alone does not establish inactivity.

Project backingcaution

The repository is owned by the same individual namespace as the package, with no organization backing shown. This is consistent ownership but leaves a narrow support base.

Repo popularitycaution

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these values provide little external evidence of active community use.