Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-02 10:44 UTC

hhszzzz / taibu

🔮 高精度AI算命工具,涵盖八字、紫微斗数、六爻、梅花易数、奇门遁甲、大六壬、小六壬、占星术、太乙神数、塔罗、MBTI、面相手相、合盘配对、每日/每月运势、周公解梦等。支持MCP服务和Skills

TypeScriptCustom license★ 518 stars⑂ 106 forkssince Jan 2026View on GitHub ↗
KindWeb interfaceNetwork serviceMobile applicationCommand-line toolMCP serverLibraryhow this is determined

hhszzzz/taibu holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (84/100) and lowest on Vitality (32/100). It was last updated 32 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

yangPersonal account
15 followers14 public repossince Oct 2021

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

Package ecosystems

Metrics by category

Vitality

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

32At Risk · 21% of overall
How it's scored
18/36Push recencylast push 32 days ago
10.4/36Commit cadence15/52 weeks with commits
18/18Commit volume538 commits in the last year
7/10OpenSSF Scorecard: Maintained6 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year538
human_commit_share1
days_since_last_push32
active_weeks_last_year15
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

56Moderate · 17% of overall
How it's scored
44/60Stars518 stars
16.8/25Forks106 forks
0/15Watchers2 watchers
Inputs used
forks106
stars518
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
45.7/80Monthly downloads2,664 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagestaibu-mcp, taibu-core, taibu-mcp-server
dependents
ecosystemsnpm
total_downloads
monthly_downloads2,664
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?

51Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
31.5/42Issue resolution75% of issues closed
30/30PR acceptance5/5 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs5
open_issues2
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.75
closed_unmerged_prs0
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.7/25Owner reach15 followers of hhszzzz
18.3/25Track record14 public repos, account ~4 yr old
Inputs used
followers15
owner_typeUser
is_verified
owner_loginhhszzzz
public_repos14
account_age_days1,781
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable3 package(s) on npm
35/35Publish recencylatest publish 34 days ago
12/20Version history3 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestaibu-mcp, taibu-core, taibu-mcp-server
ecosystemsnpm
any_deprecatedno
min_days_since_publish34

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configeslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://mingai.fun
10/10Repository description
10/10Topics16 topics
0/10Wiki
Inputs used
topicsbazi, divination, fortune-teller, liuyao, mbti, mcp, skills, tarot, ziweidoushu, liuren, qimendunjia, meihua, meihua-yishu, astrology, taiyi, xiaoliuren
has_wikino
homepagehttps://mingai.fun
docs_sitehttps://mingai.fun
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

42Weak · 16% of overall
How it's scored
6.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 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.2/2.5Licenselicense file detected
5.2/7.5Maintained6 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 7
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities147 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate2.7
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages28
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:taibu-mcp@3.5.0 runtime dependency closure — what installing the published package pulls in — 28 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.

70Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history89 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.89
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes7,626
How it's scored
12.6/18One-command bootstrapandroid/app/build.gradle, android/build.gradle (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format configeslint.config.mjs
11/11Static type checkingpackages/core/tsconfig.json, packages/mcp-server/tsconfig.json, packages/mcp/tsconfig.json, 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
lockfilespnpm-lock.yaml
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configspackages/core/tsconfig.json, packages/mcp-server/tsconfig.json, packages/mcp/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifestsandroid/app/build.gradle, android/build.gradle
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.9/55Manageable file sizes2/845 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes116,927
source_files_sampled845
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalyes
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

518GitHub stars
1contributors
538commits, last 12 months
32days since last push
0releases
1bus factor
2open issues
Maven, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 106 ⇿
0Stars
106Forks

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.

02040608010012010552026-032026-062026-08
OpenSSF Scorecard 2.7 / 10
2.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-09-02 10:44 UTC

9Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 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
9Licenselicense file detected
7Maintained6 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 7
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities147 existing vulnerabilities detected
Direct dependencies 39
RegistryPackageVersion constraintManifest
npm@ai-sdk/openai^3.0.48package.json
npm@capacitor/android^8.0.1package.json
npm@capacitor/cli^8.0.1package.json
npm@capacitor/core^8.0.1package.json
npm@capacitor/ios^8.0.1package.json
npm@lobehub/icons^4.0.2package.json
npm@phosphor-icons/react^2.1.10package.json
npm@supabase/ssr^0.8.0package.json
npm@supabase/supabase-js^2.89.0package.json
npm@tanstack/react-query^5.95.2package.json
npm@tanstack/react-virtual^3.13.18package.json
npm@vercel/analytics^1.6.1package.json
npmai^6.0.137package.json
npmhtml2canvas^1.4.1package.json
npmiztro^2.5.4package.json
npmlucide-react^0.562.0package.json
npmlunar-javascript^1.7.7package.json
npmnext16.1.1package.json
npmreact19.2.3package.json
npmreact-dom19.2.3package.json
npmreact-markdown^10.1.0package.json
npmrecharts^3.6.0package.json
npmremark-gfm^4.0.1package.json
npmtaibu-coreworkspace:*package.json
npmcircular-natal-horoscope-js^1.1.0packages/core/package.json
npmiztro^2.5.4packages/core/package.json
npmliuren-ts-lib^1.9.0packages/core/package.json
npmlunar-javascript^1.7.7packages/core/package.json
npmpinyin^4.0.0packages/core/package.json
npmtaobi^0.4.5packages/core/package.json
npmtyme4ts^1.4.4packages/core/package.json
npmtaibu-coreworkspace:*packages/mcp-server/package.json
npm@modelcontextprotocol/node2.0.0packages/mcp-server/package.json
npm@modelcontextprotocol/server2.0.0packages/mcp-server/package.json
npmdotenv^17.2.3packages/mcp-server/package.json
npmexpress^4.21.0packages/mcp-server/package.json
npmhono^4.11.4packages/mcp-server/package.json
npmtaibu-coreworkspace:*packages/mcp/package.json
npm@modelcontextprotocol/server2.0.0packages/mcp/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

Dependency advisories 0

Installing npm:taibu-mcp@3.5.0 pulls in 28 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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