Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-10 11:29 UTC

xingkaixin / agent-dump

AI Coding Assistant Session Export Tool

Rust · PythonMIT★ 8 stars⑂ 0 forkssince Feb 2026View on GitHub ↗
KindCommand-line toolTerminal interfaceWeb interfacehow this is determined

xingkaixin/agent-dump holds a health index of 73 out of 100, placing it in the Good band. It scores highest on AI Readiness (95/100) and lowest on Community & Adoption (37/100). It was last updated today. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

KevinPersonal account
29 followers119 public repossince Jan 2013

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
PyPIagent-dump1.2.22,494570 days agoaichatexportopencodecli

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
19.4/36Commit cadence — 28/52 weeks with commits
18/18Commit volume — 625 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year625
human_commit_share0.8
days_since_last_push0
active_weeks_last_year28
How it's scored
27/27Ships releases — 45 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~3 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count45
latest_release_tagv1.2.2
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases3

Community & Adoption

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

37Weak · 17% of overall
How it's scored
13.7/60Stars — 8 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars8
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
45.3/80Monthly downloads — 2,494 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesagent-dump
dependents—
ecosystemspypi
total_downloads—
monthly_downloads2,494
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?

54Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — no issues or no data
29.7/30PR acceptance — 467/471 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs467
open_issues0
closed_issues0
prs_merged_7d38
prs_decided_7d38
prs_merged_30d57
prs_decided_30d57
issue_closed_ratio—
closed_unmerged_prs4
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
10.6/25Owner reach — 29 followers of xingkaixin
25/25Track record — 119 public repos, account ~13 yr old
Inputs used
followers29
owner_typeUser
is_verified—
owner_loginxingkaixin
public_repos119
account_age_days5,004
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 0 days ago
20/20Version history — 57 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesagent-dump
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — Cargo.toml ([lints], [workspace.lints]), ruff.toml, rustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 29 out of 29 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 site — https://agent-dump.xingkaixin.me
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://agent-dump.xingkaixin.me
docs_sitehttps://agent-dump.xingkaixin.me
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

47Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 29 out of 29 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
1.5/7.5Vulnerabilities — 8 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.7

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.

95Exceptional · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt present
40/40Legible commit history — 80 of 80 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share1
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes5,248
How it's scored
18/18One-command bootstrap — justfile, mise.toml
22/22Automated tests
11/11Lint / format config — Cargo.toml ([lints], [workspace.lints]), ruff.toml, rustfmt.toml
11/11Static type checking — web/tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 20 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, pnpm-lock.yaml, uv.lock
has_dockerfileno
typed_languageyes
bootstrap_filesjustfile, mise.toml
has_devcontainerno
has_linter_configyes
typecheck_configsweb/tsconfig.json
agent_commit_share0
toolchain_manifestsCargo.toml, crates/agent-dump-core/Cargo.toml
dependency_bot_commit_share0.2
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/211 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes42,961
source_files_sampled211
oversized_source_files0

Key facts

8GitHub stars
1contributors
625commits, last 12 months
0days since last push
45releases
1bus factor
0open issues
crates.io, npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'agent-dump' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index pypi:agent-dump@1.2.2; advisories assessed against the repository dependency graph instead

More detail

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-10 11:28 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests29 out of 29 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 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
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
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
2Vulnerabilities8 existing vulnerabilities detected
Direct dependencies 25
RegistryPackageVersion constraintManifest
crates.ioagent-dump-core—Cargo.toml
crates.iojiff—Cargo.toml
crates.ioclap—Cargo.toml
crates.ioserde—Cargo.toml
crates.ioserde_json—Cargo.toml
crates.ioregex—Cargo.toml
crates.ioureq—Cargo.toml
crates.iourl—Cargo.toml
crates.iocaseless—Cargo.toml
crates.iouuid—Cargo.toml
crates.ioratatui—Cargo.toml
crates.iocrossterm—Cargo.toml
crates.iounicode-width—Cargo.toml
crates.iounicode-normalization—Cargo.toml
npm@astrojs/react^7.0.0web/package.json
npm@astrojs/sitemap^3.7.4web/package.json
npm@base-ui/react^1.8.0web/package.json
npm@fontsource-variable/geist^5.3.0web/package.json
npm@fontsource/ibm-plex-mono^5.3.0web/package.json
npm@phosphor-icons/react^2.1.10web/package.json
npm@tailwindcss/vite^4.3.3web/package.json
npmastro^7.3.5web/package.json
npmreact^19.3.0web/package.json
npmreact-dom^19.3.0web/package.json
npmtailwindcss^4.3.3web/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.34.0 — full methodology · metrics wiki.

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