Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-18 23:51 UTC

rishijatia / fantasy-pl-mcp

Fantasy Premier League MCP Server

PythonMIT★ 80 stars⑂ 24 forkssince Mar 2025View on GitHub ↗
KindLibraryCommand-line toolMCP serverhow this is determined

rishijatia/fantasy-pl-mcp holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Vitality (62/100) and lowest on AI Readiness (37/100). It was last updated 76 days ago. A single contributor accounts for most of its recent work.

57
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.

57
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 55 is calibrated to 57 on the published index scale (record calibration 2026-08-02).

Ownership

Rishi JatiaPersonal account
17 followers20 public repossince Nov 2014Microsoft

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIfpl-mcp0.1.7408876 days agofantasy-premier-leaguefplmcpclaudeaifootballsoccer

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
18/36Push recency — last push 76 days ago
2.1/36Commit cadence — 3/52 weeks with commits
12.4/18Commit volume — 23 commits in the last year
10/10OpenSSF Scorecard: Maintained — 23 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year23
human_commit_share1
days_since_last_push76
active_weeks_last_year3
How it's scored
27/27Ships releases — 7 releases published
36/36Release recency — latest release 76 days ago
19.8/27Release cadence — a release every ~84.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tagv0.1.7
releases_from_tagsno
days_since_latest_release76
mean_days_between_releases84.4
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

52Moderate · 17% of overall
How it's scored
30.8/60Stars — 80 stars
11.3/25Forks — 24 forks
0/15Watchers — 1 watchers
Inputs used
forks24
stars80
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com, shields.io
has_pull_request_templateno
How it's scored
34.8/80Monthly downloads — 408 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesfpl-mcp
dependents—
ecosystemspypi
total_downloads—
monthly_downloads408
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.2/22.5Commit distribution — top contributor authored 81% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.814
How it's scored
31.5/42Issue resolution — 75% of issues closed
26/30PR acceptance — 13/15 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 5/11 approved changesets -- score normalized to 4
Inputs used
merged_prs13
open_issues2
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.75
closed_unmerged_prs2
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
9/25Owner reach — 17 followers of rishijatia
21.6/25Track record — 20 public repos, account ~11 yr old
Inputs used
followers17
owner_typeUser
is_verified—
owner_loginrishijatia
public_repos20
account_age_days4,361
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 76 days ago
20/20Version history — 8 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesfpl-mcp
ecosystemspypi
any_deprecatedno
min_days_since_publish76

Engineering Quality

Are baseline engineering and documentation practices in place?

51Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests — 2 out of 8 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

55Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0.5/2.5CI-Tests — 2 out of 8 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 5/11 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 23 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
26.6/35Direct dependencies free of known advisories — 1 affected: diskcache 5.6.3 (moderate)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
37.2/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 249 days ago
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages33
unassessed_packages0
affected_by_severitymoderate 1
direct_affected_packages1
Matched the pypi:fpl-mcp@0.1.7 runtime dependency closure — what installing the published package pulls in — 33 packages. Reachability is not analyzed.

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.

37Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
22.9/40Legible commit history — 30 of 70 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.429
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 12 of the last 70 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.171
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/52 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes45,129
source_files_sampled52
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

80GitHub stars
3contributors
23commits, last 12 months
76days since last push
7releases
1bus factor
2open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 24 ⇿
0Stars
24Forks
4Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

048121620242422025-032025-122026-08
Major 0Minor 0Patch 4

Each point covers 2 days.

OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-10-18 23:51 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
2CI-Tests2 out of 8 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 5/11 approved changesets -- score normalized to 4
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained23 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
PyPImcp>=1.2.0,<2.0.0pyproject.toml
PyPIhttpx>=0.24.0pyproject.toml
PyPIpython-dotenv—pyproject.toml
PyPIdiskcache—pyproject.toml
PyPIjsonschema—pyproject.toml
PyPIrequests—pyproject.toml
PyPIcryptography—pyproject.toml
All dependencies 76

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

RegistryPackageVersionRelation
PyPIcryptography44.0.2direct
PyPIdiskcache5.6.3direct
PyPIhttpx0.28.1direct
PyPIjsonschema4.23.0direct
PyPImcp1.4.1direct
PyPIpython-dotenv1.0.1direct
PyPIrequests—direct
PyPIrequests2.32.3direct
PyPIannotated-types0.7.0indirect
PyPIanyio4.8.0indirect
PyPIattrs25.3.0indirect
PyPIbackports-tarfile1.2.0indirect
PyPIblack25.1.0indirect
PyPIbuild1.2.2.post1indirect
PyPIcertifi2025.1.31indirect
PyPIcffi1.17.1indirect
PyPIcharset-normalizer3.4.1indirect
PyPIclick8.1.8indirect
PyPIcolorama0.4.6indirect
PyPIdocutils0.21.2indirect
PyPIexceptiongroup1.2.2indirect
PyPIflake87.1.2indirect
PyPIfpl-mcp0.1.6indirect
PyPIh110.14.0indirect
PyPIhttpcore1.0.7indirect
PyPIhttpx-sse0.4.0indirect
PyPIid1.5.0indirect
PyPIidna3.10indirect
PyPIimportlib-metadata8.6.1indirect
PyPIiniconfig2.0.0indirect
PyPIisort6.0.1indirect
PyPIjaraco-classes3.4.0indirect
PyPIjaraco-context6.0.1indirect
PyPIjaraco-functools4.1.0indirect
PyPIjeepney0.9.0indirect
PyPIjsonschema-specifications2024.10.1indirect
PyPIkeyring25.6.0indirect
PyPImarkdown-it-py3.0.0indirect
PyPImccabe0.7.0indirect
PyPImdurl0.1.2indirect
PyPImore-itertools10.6.0indirect
PyPImypy1.15.0indirect
PyPImypy-extensions1.0.0indirect
PyPInh30.2.21indirect
PyPIpackaging24.2indirect
PyPIpathspec0.12.1indirect
PyPIplatformdirs4.3.6indirect
PyPIpluggy1.5.0indirect
PyPIpycodestyle2.12.1indirect
PyPIpycparser2.22indirect
PyPIpydantic2.10.6indirect
PyPIpydantic-core2.27.2indirect
PyPIpydantic-settings2.8.1indirect
PyPIpyflakes3.2.0indirect
PyPIpygments2.19.1indirect
PyPIpyproject-hooks1.2.0indirect
PyPIpytest8.3.5indirect
PyPIpywin32-ctypes0.2.3indirect
PyPIreadme-renderer44.0indirect
PyPIreferencing0.36.2indirect
PyPIrequests-toolbelt1.0.0indirect
PyPIrfc39862.0.0indirect
PyPIrich13.9.4indirect
PyPIrpds-py0.23.1indirect
PyPIsecretstorage3.3.3indirect
PyPIshellingham1.5.4indirect
PyPIsniffio1.3.1indirect
PyPIsse-starlette2.2.1indirect
PyPIstarlette0.46.1indirect
PyPItomli2.2.1indirect
PyPItwine6.1.0indirect
PyPItyper0.15.2indirect
PyPItyping-extensions4.12.2indirect
PyPIurllib32.3.0indirect
PyPIuvicorn0.34.0indirect
PyPIzipp3.21.0indirect
Dependency advisories 1

Installing pypi:fpl-mcp@0.1.7 pulls in 33 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
diskcache5.6.3directmoderate2—

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.34.0 — full methodology · metrics wiki.

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