Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 01:13 UTC

lss233 / kirara-ai

🤖 可 DIY 的 多模态 AI 聊天机器人 | 🚀 快速接入 微信、 QQ、Telegram、等聊天平台 | 🦈支持DeepSeek、Grok、Claude、Ollama、Gemini、OpenAI | 工作流系统、网页搜索、AI画图、人设调教、虚拟女仆、语音对话 |

PythonAGPL-3.0★ 19,025 stars⑂ 1,836 forkssince Dec 2022View on GitHub ↗
KindCommand-line toolMCP serverNetwork serviceChat bothow this is determined

lss233/kirara-ai holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Engineering Quality (78/100) and lowest on Vitality (25/100). It was last updated 447 days ago. A single contributor accounts for most of its recent work.

48
overall / 100
Weak

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.

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

Ownership

Dark LitssPersonal account
823 followers80 public repossince Oct 2014

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 publish
PyPIkirara-aipoints to another repo — not scored3.2.0929531 days ago

Metrics by category

Vitality

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

25At Risk · 21% of overall
How it's scored
0/36Push recencylast push 447 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push447
active_weeks_last_year0
How it's scored
27/27Ships releases74 releases published
7.2/36Release recencylatest release 501 days ago
27/27Release cadencea release every ~9.4 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count74
latest_release_tagv3.3.0a2
releases_from_tagsno
days_since_latest_release501
mean_days_between_releases9.4

Community & Adoption

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

75Good · 17% of overall
How it's scored
60/60Stars19,025 stars
25/25Forks1,836 forks
11.2/15Watchers104 watchers
Inputs used
forks1,836
stars19,025
watchers104
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (AGPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges10
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

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 factor1 contributor(s) cover half of all commits
3/22.5Commit distributiontop contributor authored 87% of commits
13.5/13.5Contributor breadth38 contributors
10/10OpenSSF Scorecard: Contributorsproject has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled38
top_contributor_share0.866
How it's scored
41.9/42Issue resolution100% of issues closed
20.3/30PR acceptance219/324 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 3/10 approved changesets -- score normalized to 3
Inputs used
merged_prs219
open_issues2
closed_issues1,110
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.998
closed_unmerged_prs105
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
21/25Owner reach823 followers of lss233
25/25Track record80 public repos, account ~11 yr old
Inputs used
followers823
owner_typeUser
is_verified
owner_loginlss233
public_repos80
account_age_days4,370
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
16/16Linter config.pylintrc
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 7 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://kirara-docs.app.lss233.com/
10/10Repository description
10/10Topics20 topics
10/10Wiki
Inputs used
topicschatgpt, openai, qq, qqbot, bot, new-bing, sydney, bard, discord, ernie, poe, chatglm-6b, go-cqhttp, mirai, telegram, wechat, xinghuo, deepseek, ollama, grok
has_wikiyes
homepagehttps://kirara-docs.app.lss233.com/
docs_sitehttps://kirara-docs.app.lss233.com/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

32At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 7 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 3/10 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 7 contributing companies or organizations
0/10Dangerous-Workflowdangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.2
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

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.

60Moderate · 4% of overall
How it's scored
45/45Agent instructions.cursor/rules/create-workflow.mdc
0/15Machine-readable docs (llms.txt)
40/40Legible commit history91 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.91
agent_instruction_files.cursor/rules/create-workflow.mdc
agent_instruction_max_bytes3,366
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.pylintrc
0/11Static type checking
10/10Reproducible environmentDockerfile
10/10Demonstrated agent practice5 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.05
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/288 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes24,029
source_files_sampled288
oversized_source_files0
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_ofchat-bot, network-service

Key facts

19,025GitHub stars
38contributors
0commits, last 12 months
447days since last push
74releases
1bus factor
2open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi package 'kirara-ai' points at a different repository (https://github.com/lss233/chatgpt-mirai-qq-bot); excluded from ecosystem scoring
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 1,836 ⇿
0Stars
1,836Forks
12Releases

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.

5001,0001,5002,0001,836172023-062025-012026-09
Major 0Minor 1Patch 3

Each point covers 3 days.

OpenSSF Scorecard 3.2 / 10
3.2aggregate

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-19 01:12 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
0CI-Tests0 out of 7 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 3/10 approved changesets -- score normalized to 3
10Contributorsproject has 7 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 35
RegistryPackageVersion constraintManifest
PyPIpydantic>=2.0.0pyproject.toml
PyPIpydantic-core>=2.27.2pyproject.toml
PyPIruamel.yamlpyproject.toml
PyPIpytestpyproject.toml
PyPIpytest-asynciopyproject.toml
PyPIpython-telegram-botpyproject.toml
PyPItelegramify-markdownpyproject.toml
PyPIlogurupyproject.toml
PyPIaiohttppyproject.toml
PyPIrequestspyproject.toml
PyPIquart>=0.18.4pyproject.toml
PyPIquart-cors>=0.7.0pyproject.toml
PyPIfastapi>=0.110.0pyproject.toml
PyPIwechatpypyproject.toml
PyPIpycryptodomepyproject.toml
PyPIredispyproject.toml
PyPIbcrypt>=4.0.1pyproject.toml
PyPIPyJWT>=2.8.0pyproject.toml
PyPIhypercorn>=0.15.0pyproject.toml
PyPIpsutil>=5.9.0pyproject.toml
PyPIsetuptoolspyproject.toml
PyPItomli>=2.0.0pyproject.toml
PyPIpre-commitpyproject.toml
PyPIcurl_cffipyproject.toml
PyPIpython-magicpyproject.toml
PyPIpython-magic-binpyproject.toml
PyPIymbotpypyproject.toml
PyPIPillowpyproject.toml
PyPIpytzpyproject.toml
PyPIsqlalchemypyproject.toml
PyPIalembicpyproject.toml
PyPImcppyproject.toml
PyPIpyglspyproject.toml
PyPIjedipyproject.toml
PyPIpyflakespyproject.toml
All dependencies 35

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

RegistryPackageVersionRelation
PyPIaiohttpdirect
PyPIalembicdirect
PyPIbcryptdirect
PyPIcurl-cffidirect
PyPIfastapidirect
PyPIhypercorndirect
PyPIjedidirect
PyPIlogurudirect
PyPImcpdirect
PyPIpillowdirect
PyPIpre-commitdirect
PyPIpsutildirect
PyPIpycryptodomedirect
PyPIpydanticdirect
PyPIpydantic-coredirect
PyPIpyflakesdirect
PyPIpyglsdirect
PyPIpyjwtdirect
PyPIpytestdirect
PyPIpytest-asynciodirect
PyPIpython-magicdirect
PyPIpython-magic-bindirect
PyPIpython-telegram-botdirect
PyPIpytzdirect
PyPIquartdirect
PyPIquart-corsdirect
PyPIredisdirect
PyPIrequestsdirect
PyPIruamel-yamldirect
PyPIsetuptoolsdirect
PyPIsqlalchemydirect
PyPItelegramify-markdowndirect
PyPItomlidirect
PyPIwechatpydirect
PyPIymbotpydirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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