Public record
Software health reportschema 0.32.0 · metrics 2.10.0 · 2026-08-20 00:32 UTC

twjackysu / TWSEMCPServer

台灣證交所OpenAPI 的 MCP Server 同時整合部分即時報價和櫃檯買賣中心TPEx OpenAPI, 臺灣期貨交易所TAIFEX OpenAPI

PythonMIT★ 148 stars⑂ 41 forkssince Jun 2025View on GitHub ↗

twjackysu/TWSEMCPServer holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (87/100) and lowest on Security (46/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Jacky SuPersonal account
14 followers32 public repossince Jun 2017

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?

87Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
15.2/36Commit cadence22/52 weeks with commits
18/18Commit volume154 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year154
human_commit_share1
days_since_last_push1
active_weeks_last_year22

Release discipline

100Exceptional
How it's scored
27/27Ships releases13 releases published
36/36Release recencylatest release 31 days ago
27/27Release cadencea release every ~9.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count13
latest_release_tagv1.8.0
releases_from_tagsno
days_since_latest_release31
mean_days_between_releases9.3
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?

49Weak · 17% of overall
How it's scored
35.2/60Stars148 stars
13.4/25Forks41 forks
0/15Watchers0 watchers
Inputs used
forks41
stars148
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

47Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.9/22.5Commit distributiontop contributor authored 96% of commits
5.4/13.5Contributor breadth4 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.958
How it's scored
40.2/42Issue resolution96% of issues closed
28.5/30PR acceptance38/40 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/13 approved changesets -- score normalized to 0
Inputs used
merged_prs38
open_issues1
closed_issues23
prs_merged_7d1
prs_decided_7d1
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.958
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
8.5/25Owner reach14 followers of twjackysu
23.1/25Track record32 public repos, account ~9 yr old
Inputs used
followers14
owner_typeUser
is_verified
owner_logintwjackysu
public_repos32
account_age_days3,344
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
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
10/10Topics5 topics
0/10Wiki
Inputs used
topicsanalysis, mcp, mcp-server, questions-and-answers, trading
has_wikino
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?

46Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 1/13 approved changesets -- score normalized to 0
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 2 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
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities50 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.6
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.
How it's scored
5.3/35Direct dependencies free of known advisories3 affected: fastmcp 2.12.3 (critical 10.0), mcp 1.27.0 (high 7.6), requests 2.32.4 (moderate 5.5)
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
28.8/40No advisories left outstanding2 advisory-carrying package(s) unaddressed past 90 days; oldest published 294 days ago
Inputs used
sourceosv
advisories93
affected_packages15
assessed_packages76
unassessed_packages5
affected_by_severitycritical 2, high 7, moderate 5, low 1
direct_affected_packages3
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 76 resolved dependencies against OSV. 5 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

56Moderate · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history97 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.97
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes12,651
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice8 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.08
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/103 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes20,874
source_files_sampled103
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

148GitHub stars
4contributors
154commits, last 12 months
1days since last push
13releases
1bus factor
1open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch pypi package 'twstockmcpserver' from its registry

More detail

Star and fork history 0 ★ / 41 ⇿
0Stars
41Forks
13Releases

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.

010203040504122025-072026-022026-08
Major 1Minor 8Patch 4
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-08-20 00:31 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/13 approved changesets -- score normalized to 0
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 2 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
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities50 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
PyPIfastmcp==2.12.3pyproject.toml
PyPIhttpx>=0.28.1pyproject.toml
PyPImcp>=1.9.3pyproject.toml
PyPIrequests>=2.32.4pyproject.toml
All dependencies 81

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

RegistryPackageVersionRelation
PyPIfastmcp2.12.3direct
PyPIhttpx0.28.1direct
PyPImcpdirect
PyPImcp1.27.0direct
PyPIrequests2.32.4direct
PyPIannotated-types0.7.0indirect
PyPIanyio4.9.0indirect
PyPIattrs25.3.0indirect
PyPIauthlib1.7.0indirect
PyPIcertifi2025.7.14indirect
PyPIcffi1.17.1indirect
PyPIcharset-normalizer3.4.2indirect
PyPIclick8.2.2indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.11.0indirect
PyPIcryptography45.0.5indirect
PyPIcyclopts4.11.0indirect
PyPIdnspython2.7.0indirect
PyPIdocstring-parser0.17.0indirect
PyPIdocutils0.22indirect
PyPIemail-validator2.2.0indirect
PyPIexceptiongroup1.3.0indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx-sse0.4.1indirect
PyPIidna3.10indirect
PyPIiniconfig2.1.0indirect
PyPIisodate0.7.2indirect
PyPIjoserfc1.6.4indirect
PyPIjsonschema4.25.0indirect
PyPIjsonschema-path0.4.5indirect
PyPIjsonschema-specifications2025.4.1indirect
PyPIlazy-object-proxy1.12.0indirect
PyPImarkdown-it-py3.0.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdurl0.1.2indirect
PyPImore-itertools10.7.0indirect
PyPIopenapi-core0.23.1indirect
PyPIopenapi-pydantic0.5.1indirect
PyPIopenapi-schema-validator0.8.1indirect
PyPIopenapi-spec-validator0.8.5indirect
PyPIpackaging25.0indirect
PyPIpathable0.5.0indirect
PyPIpluggy1.6.0indirect
PyPIpycparser2.22indirect
PyPIpydantic2.11.7indirect
PyPIpydantic-core2.33.2indirect
PyPIpydantic-settings2.10.1indirect
PyPIpygments2.19.2indirect
PyPIpyjwt2.12.1indirect
PyPIpyperclip1.9.0indirect
PyPIpytestindirect
PyPIpytest8.4.2indirect
PyPIpytest-asyncioindirect
PyPIpytest-asyncio1.2.0indirect
PyPIpytest-covindirect
PyPIpytest-cov7.0.0indirect
PyPIpytest-mockindirect
PyPIpytest-mock3.15.1indirect
PyPIpytest-rerunfailures16.2indirect
PyPIpython-dotenv1.1.1indirect
PyPIpython-multipart0.0.20indirect
PyPIpywin32311indirect
PyPIpyyaml6.0.2indirect
PyPIreferencing0.37.0indirect
PyPIrfc3339-validator0.1.4indirect
PyPIrich14.1.0indirect
PyPIrich-rst1.3.1indirect
PyPIrpds-py0.26.0indirect
PyPIshellingham1.5.4indirect
PyPIsix1.17.0indirect
PyPIsniffio1.3.1indirect
PyPIsse-starlette3.0.2indirect
PyPIstarlette0.47.2indirect
PyPItwstockmcpserver0.1.0indirect
PyPItyper0.16.0indirect
PyPItyping-extensions4.15.0indirect
PyPItyping-inspection0.4.1indirect
PyPIurllib32.5.0indirect
PyPIuvicorn0.35.0indirect
PyPIwerkzeug3.1.8indirect
Dependency advisories 15

This repository publishes no package the index resolves, so its own dependency graph was assessed — 76 packages, which also include development and test pins that never ship: 15 carry known advisories, of which 3 are direct. 5 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
fastmcp2.12.3directcritical143.2.0
cryptography45.0.5indirectcritical1350.0.0
mcp1.27.0directhigh61.28.1
click8.2.2indirecthigh18.3.3
joserfc1.6.4indirecthigh41.6.8
pyjwt2.12.1indirecthigh92.13.0
python-multipart0.0.20indirecthigh140.0.31
starlette0.47.2indirecthigh121.3.1
urllib32.5.0indirecthigh82.7.0
requests2.32.4directmoderate22.33.0
authlib1.7.0indirectmoderate21.7.1
idna3.10indirectmoderate23.15
pytest8.4.2indirectmoderate29.0.3
python-dotenv1.1.1indirectmoderate21.2.2
pygments2.19.2indirectlow22.20.0

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

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