lukasss93/minecraft-server-status

Project backingcaution

The package and repository are owned by the same individual account, so the ownership context is consistent. A single-person project offers less organizational maintenance redundancy than a backed organization, but no mismatch is shown.

Release historycaution

The package has made only two releases, both about eight years ago, with no release in the last 12 months. This is the clearest sign of limited ongoing maintenance, although the linked repository was updated later.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. Combined with the long registry release gap, this points to reduced current maintenance capacity.

Repo issue activitycaution

One issue and one pull request remain open, with no issues or pull requests opened or closed in the last month. This is mild evidence of limited current responsiveness, not abandonment by itself.

Repo toolingcaution

Composer build tooling is present, but no repository security-scanning tools were detected. That leaves a modest transparency and maintenance-hygiene gap.