matthewlefevre/ken-framework

Release historydanger

The package has had no release in over six years despite 13 releases during its initial 3-month development period. That long release gap is strong evidence of abandonment risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the package's multi-year release gap. This is the main maintenance and abandonment concern.

Maintainerscaution

Only one registry account has publish access. That is a thin operational base for a user-owned project and offers little resilience if the sole maintainer becomes unavailable.

Project backingcaution

The package and repository are owned by the same individual account rather than an organization. That is consistent ownership, but it provides no organizational backing to compensate for the single-maintainer and inactivity concerns.

Repo popularitycaution

The repository has only 1 star and 1 fork, so there is little community evidence to compensate for the lack of recent maintenance. Popularity is supporting evidence rather than a verdict, but here it does not offset the stronger inactivity signals.