Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 20:44 UTC

macarooni-man / auto-mcs

Cross-platform Minecraft server manager

PythonGPL-3.0★ 473 stars⑂ 33 forkssince May 2023View on GitHub ↗

macarooni-man/auto-mcs holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Vitality (89/100) and lowest on AI Readiness (13/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

60
overall / 100
Moderate

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

60
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 57 is calibrated to 60 on the published index scale (record calibration 2026-08-02).

Ownership

Kaleb EfflandtPersonal account
19 followers8 public repossince Oct 2020

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

89Excellent · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
29.1/36Commit cadence42/52 weeks with commits
18/18Commit volume656 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year656
human_commit_share
days_since_last_push3
active_weeks_last_year42
How it's scored
27/27Ships releases29 releases published
36/36Release recencylatest release 3 days ago
19.8/27Release cadencea release every ~48.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count29
latest_release_tagv2.3.9
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases48.7

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

64Moderate · 17% of overall
How it's scored
43.4/60Stars473 stars
12.5/25Forks33 forks
2.7/15Watchers4 watchers
Inputs used
forks33
stars473
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (GPL-3.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

45Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.1/22.5Commit distributiontop contributor authored 100% of commits
6.8/13.5Contributor breadth5 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.995
How it's scored
35.9/42Issue resolution86% of issues closed
26.4/30PR acceptance81/92 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 2/5 approved changesets -- score normalized to 4
Inputs used
merged_prs81
open_issues26
closed_issues153
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.855
closed_unmerged_prs11
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
9.4/25Owner reach19 followers of macarooni-man
18.5/25Track record8 public repos, account ~5 yr old
Inputs used
followers19
owner_typeUser
is_verified
owner_loginmacarooni-man
public_repos8
account_age_days2,108
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests3 out of 5 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://www.auto-mcs.com
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicsminecraft, minecraft-server, api, easy, backup, modding, amscript
has_wikino
homepagehttps://www.auto-mcs.com
docs_sitehttps://www.auto-mcs.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

46Weak · 16% of overall
How it's scored
3.8/7.5Binary-Artifactsbinaries present in source code
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1.5/2.5CI-Tests3 out of 5 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 2/5 approved changesets -- score normalized to 4
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
3.5/5SASTSAST tool is not run on all commits -- score normalized to 7
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.6

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

13Critical · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePython without a type-check config
37.6/55Manageable file sizes18/57 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes221,186
source_files_sampled57
oversized_source_files18

Key facts

473GitHub stars
5contributors
656commits, last 12 months
3days since last push
29releases
1bus factor
26open issues
package ecosystems

More detail

OpenSSF Scorecard 4.6 / 10
4.6aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-07-17 20:43 UTC

5Binary-Artifactsbinaries present in source code
5Branch-Protectionbranch protection is not maximal on development and all release branches
6CI-Tests3 out of 5 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 2/5 approved changesets -- score normalized to 4
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
7SASTSAST tool is not run on all commits -- score normalized to 7
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 35

Full resolved dependency set from the GitHub dependency graph: 0 direct and 35 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
PyPIaltgraph0.17.3indirect
PyPIasyncio-dgram2.1.2indirect
PyPIbeautifulsoup44.11.1indirect
PyPIcertifi2023.7.22indirect
PyPIcharset-normalizer2.1.1indirect
PyPIcloudscraper1.2.69indirect
PyPIdnspython2.2.1indirect
PyPIdocutils0.19indirect
PyPIfuture0.18.3indirect
PyPIidna3.4indirect
PyPIipaddress1.0.23indirect
PyPIkivy2.0.0indirect
PyPIkivy-deps-angle0.3.2indirect
PyPIkivy-deps-glew0.3.1indirect
PyPIkivy-deps-sdl20.3.1indirect
PyPIkivy-garden0.1.5indirect
PyPImunch3.0.0indirect
PyPInbt1.5.1indirect
PyPIpefile2022.5.30indirect
PyPIpillow10.0.1indirect
PyPIplyer2.0.0indirect
PyPIpsutil5.9.2indirect
PyPIpygments2.16.1indirect
PyPIpyinstaller6.1.0indirect
PyPIpyinstaller-hooks-contrib2022.10indirect
PyPIpyparsing3.0.9indirect
PyPIpypiwin32223indirect
PyPIpywin32304indirect
PyPIpywin32-ctypes0.2.0indirect
PyPIrequests2.31.0indirect
PyPIrequests-toolbelt0.10.0indirect
PyPIsimpleaudio1.0.4indirect
PyPIsix1.16.0indirect
PyPIsoupsieve2.3.2.post1indirect
PyPIurllib31.26.18indirect
Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.12.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics.