libeo/lbo-unbolt

Release historydanger

The package has made no release in about two years, with all three releases clustered on one day; this is strong evidence of stalled maintenance despite the absence of a deprecation notice.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, providing no evidence of current maintenance capacity.

Repo package mentioncaution

The linked repository name does not match the package name and its README does not mention the package, making package-to-source ownership less transparent even though the repository is under the same organization.

Security policycaution

The repository has no security policy, which weakens vulnerability-reporting transparency; this is a hygiene gap rather than evidence that the package is unsafe.