Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-04 23:35 UTC

ZhuLinsen / daily_stock_analysis

LLM 驱动的多市场股票智能分析系统:多源行情、实时新闻、决策看板与自动推送,支持零成本定时运行。 LLM-powered multi-market stock analysis system with multi-source market data, real-time news, decision dashboard, automated notifications, and cost-free scheduled runs.

Python · TypeScriptMIT★ 60,061 stars⑂ 51,406 forkssince Jan 2026View on GitHub ↗
KindWeb interfacehow this is determined

ZhuLinsen/daily_stock_analysis holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (88/100) and lowest on Security (41/100). It was last updated today. 2 contributors account for most of its recent work.

88
overall / 100
Excellent

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.

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

Ownership

zhulinsenPersonal account
1,535 followers37 public repossince Aug 2018

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 0 days ago
20.8/36Commit cadence30/52 weeks with commits
18/18Commit volume937 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 29 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year937
human_commit_share1
days_since_last_push0
active_weeks_last_year30
How it's scored
27/27Ships releases33 releases published
36/36Release recencylatest release 2 days ago
27/27Release cadencea release every ~6.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count33
latest_release_tagv3.29.0
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases6.7

Community & Adoption

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

88Excellent · 17% of overall
How it's scored
60/60Stars60,061 stars
25/25Forks51,406 forks
13.2/15Watchers233 watchers
Inputs used
forks51,406
stars60,061
watchers233
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

63Moderate · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.3/22.5Commit distributiontop contributor authored 50% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.496
How it's scored
40.2/42Issue resolution96% of issues closed
15.1/30PR acceptance655/1,302 decided PRs merged
0/13Newcomer PR acceptance0/10 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 14/30 approved changesets -- score normalized to 4
Inputs used
merged_prs655
open_issues34
closed_issues765
prs_merged_7d14
prs_decided_7d25
prs_merged_30d26
prs_decided_30d59
issue_closed_ratio0.957
closed_unmerged_prs647
first_time_authors_30d10
first_time_prs_merged_30d0
first_time_prs_decided_30d10
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
22.9/25Owner reach1,535 followers of ZhuLinsen
23.5/25Track record37 public repos, account ~7 yr old
Inputs used
followers1,535
owner_typeUser
is_verified
owner_loginZhuLinsen
public_repos37
account_age_days2,896
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows10 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests28 out of 28 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://dsa.zhulinsen.tech
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicsaigc, llm, quant, quantitative-trading, a-stock, ai-agent, quantitative-finance
has_wikino
homepagehttps://dsa.zhulinsen.tech
docs_sitehttps://dsa.zhulinsen.tech
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

41Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests28 out of 28 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
3/7.5Code-ReviewFound 14/30 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 11 contributing companies or organizations
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 29 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-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities132 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.1

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.

74Good · 4% of overall
How it's scored
45/45Agent instructions.github/copilot-instructions.md, .github/instructions/backend.instructions.md, .github/instructions/client.instructions.md, .github/instructions/governance.instructions.md, AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files.github/copilot-instructions.md, .github/instructions/backend.instructions.md, .github/instructions/client.instructions.md, .github/instructions/governance.instructions.md, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes17,263
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.js
11/11Static type checkingapps/dsa-web/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
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
lockfilespackage-lock.json
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsapps/dsa-web/tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codePython with type-check config (apps/dsa-web/tsconfig.json)
51.9/55Manageable file sizes49/883 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes228,423
source_files_sampled883
oversized_source_files49
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

60,061GitHub stars
99contributors
937commits, last 12 months
0days since last push
33releases
2bus factor
34open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 22 authors (cap 12)
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 51,406 ⇿
0Stars
51,406Forks
2Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

50,00050,50051,00051,50051,4061762026-072026-072026-08
Major 0Minor 2Patch 0
OpenSSF Scorecard 4.1 / 10
4.1aggregate

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-04 23:35 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests28 out of 28 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 14/30 approved changesets -- score normalized to 4
10Contributorsproject has 11 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 29 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
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities132 existing vulnerabilities detected
Direct dependencies 17
RegistryPackageVersion constraintManifest
npmelectron-updater^6.8.3apps/dsa-desktop/package.json
npm@remixicon/react^4.9.0apps/dsa-web/package.json
npmaxios^1.13.4apps/dsa-web/package.json
npmcamelcase-keys^10.0.2apps/dsa-web/package.json
npmclsx^2.1.1apps/dsa-web/package.json
npmlucide-react^0.555.0apps/dsa-web/package.json
npmmotion^12.36.0apps/dsa-web/package.json
npmnext-themes^0.4.6apps/dsa-web/package.json
npmreact^19.2.0apps/dsa-web/package.json
npmreact-dom^19.2.0apps/dsa-web/package.json
npmreact-markdown^10.1.0apps/dsa-web/package.json
npmreact-router-dom^7.13.0apps/dsa-web/package.json
npmrecharts^3.3.0apps/dsa-web/package.json
npmremark-gfm^4.0.1apps/dsa-web/package.json
npmremove-markdown^0.6.3apps/dsa-web/package.json
npmtailwind-merge^3.5.0apps/dsa-web/package.json
npmzustand^5.0.11apps/dsa-web/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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

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