moonshine/menu-manager

Maintainerscaution

Only one registry account has publish access, which is a supply-chain continuity concern, but this is partly offset by the organization-owned source repository and observed release activity.

Package scaffoldingcaution

A README is present and GitHub Releases are used, but neither the artifact nor the repository contains tests or a changelog. For a small readonly subtree split this is a real transparency and maintenance gap, although the release process provides some compensating evidence.

Repo bus factorcaution

All recent repository commits came from one contributor, creating concentration risk. Organization ownership provides some handoff capacity, but no second active contributor is shown in this signal.

Repo commit activitycaution

Only one commit was recorded in the last 3 months from one active maintainer, indicating thin recent development activity, though it is consistent with the package's recent release history.

Repo issue activitycaution

There were no new or closed issues and no pull requests in the last month; this is limited evidence of community activity, but the open-issue count is unknown and the repository is a readonly subtree split.