ghostwriter/console

Maintainerscaution

Only one registry account has publish access, which limits publishing redundancy. Because the repository is also actively maintained, this is a continuity concern rather than evidence of current neglect.

Project backingcaution

The repository is owned by the ghostwriter user account rather than an organization, so there is no organizational backing to offset the concentrated maintainer base.

Repo bus factorcaution

One contributor made all 76 commits in the last three months, creating a clear single-maintainer continuity risk with no demonstrated handoff capacity.

Repo popularitycaution

The repository has zero stars, forks, and watchers. This provides little external validation, but popularity is supporting evidence only and does not outweigh the observed release and commit activity.

Token permissionscaution

The only workflow declares top-level write permissions, which grants broader CI token authority than necessary and increases workflow-governance risk, although no dangerous workflow pattern was detected.