kaiorocha/frenet

Release historydanger

The package has had only three releases, all concentrated on 26 January 2017, with no release in nearly nine years. This is strong evidence of abandonment for a dependency that may need compatibility updates.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.

Maintainerscaution

One registry maintainer is listed, matching the individual repository ownership. This is not inherently unhealthy, but it leaves a thin maintainer base with no recent activity to demonstrate continuity.

Package file treecaution

The small artifact contains the manifest, source files, example, lockfile, and README, so its published contents are transparent and easy to inspect. The limited tree also provides little evidence of broader maintenance practice.

Project backingcaution

The package and repository are owned by the same individual account, so ownership is consistent. Individual ownership does not provide the continuity or capacity of an organization-backed project.