Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 12:57 UTC

xz333221 / zen-gitsync

Auto commit, scheduled sync, and visual GUI for Git. Run g in any repo for one-key commit & push, AI commit messages, scheduled background sync, and a drag-and-drop workflow builder.

JavaScript · Vue · HTMLCustom license★ 1 star⑂ 0 forkssince Nov 2024View on GitHub ↗
KindLibraryNetwork servicehow this is determined

xz333221/zen-gitsync holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Vitality (91/100) and lowest on Community & Adoption (32/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

xz333221Personal account
0 followers56 public repossince Aug 2017

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?

91Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
29.1/36Commit cadence42/52 weeks with commits
18/18Commit volume1,240 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,240
human_commit_share
days_since_last_push1
active_weeks_last_year42
How it's scored
16.2/27Ships releases100 version tags (no GitHub releases)
36/36Release recencylatest release 2 days ago
27/27Release cadencea release every ~0.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv2.15.27
releases_from_tagsyes
days_since_latest_release2
mean_days_between_releases0.8
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?

32At Risk · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars1
watchers1
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
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
53/80Monthly downloads9,505 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageszen-gitsync
dependents
ecosystemsnpm
total_downloads
monthly_downloads9,505
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?

34At Risk · 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
0/42Issue resolutionno issues or no data
0/30PR acceptanceno decided pull requests or no data
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_prs0
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
0/25Owner reach0 followers of xz333221
24.8/25Track record56 public repos, account ~8 yr old
Inputs used
followers0
owner_typeUser
is_verified
owner_loginxz333221
public_repos56
account_age_days3,248
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 2 days ago
20/20Version history251 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageszen-gitsync
ecosystemsnpm
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

58Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://www.npmjs.com/package/zen-gitsync
10/10Repository description
10/10Topics14 topics
10/10Wiki
Inputs used
topicsai-commit, cli, commit-message, conventional-commits, developer-tools, git, git-auto-commit, git-automation, git-cli, git-gui, git-sync, git-workflow, nodejs, productivity
has_wikiyes
homepagehttps://www.npmjs.com/package/zen-gitsync
docs_sitehttps://www.npmjs.com/package/zen-gitsync
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

37Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
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
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.7
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

62Moderate · 4% of overall
How it's scored
45/45Agent instructions.github/copilot-instructions.md, .github/instructions/i18n-check.instructions.md, .github/instructions/syntax-check.instructions.md, .github/instructions/tsc-check.instructions.md, AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files.github/copilot-instructions.md, .github/instructions/i18n-check.instructions.md, .github/instructions/syntax-check.instructions.md, .github/instructions/tsc-check.instructions.md, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes2,921
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingsrc/ui/client/tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configssrc/ui/client/tsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
27/45Type-checkable codeJavaScript with type-check config (src/ui/client/tsconfig.json)
53.2/55Manageable file sizes7/209 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes184,414
source_files_sampled209
oversized_source_files7

Key facts

1GitHub stars
1contributors
1,240commits, last 12 months
1days since last push
100releases
1bus factor
0open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 3.7 / 10
3.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-07-16 12:57 UTC

10Binary-Artifactsno binaries found in the repo
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
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
npmai-model-form^0.2.0package.json
npmboxen^8.0.1package.json
npmchalk^5.4.1package.json
npmcli-table3^0.6.5package.json
npmdate-fns^4.1.0package.json
npmexpress^5.1.0package.json
npmiconv-lite^0.7.0package.json
npmlocal-file-picker^0.2.1package.json
npmlog-update^6.1.0package.json
npmopen^10.1.2package.json
npmora^8.1.1package.json
npmpdf-parse^2.4.5package.json
npmsocket.io^4.8.1package.json
npmsocket.io-client^4.8.1package.json
npmstring-width^7.2.0package.json
All dependencies 52

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

RegistryPackageVersionRelation
npmai-model-form^0.2.0direct
npmboxen^8.0.1direct
npmchalk^5.4.1direct
npmcli-table3^0.6.5direct
npmdate-fns^4.1.0direct
npmexpress^5.1.0direct
npmiconv-lite^0.7.0direct
npmlocal-file-picker^0.2.1direct
npmlog-update^6.1.0direct
npmopen^10.1.2direct
npmora^8.1.1direct
npmpdf-parse^2.4.5direct
npmsocket.io^4.8.1direct
npmsocket.io-client^4.8.1direct
npmstring-width^7.2.0direct
npm@element-plus/icons-vue^2.3.2indirect
npm@playwright/test^1.60.0indirect
npm@tailwindcss/vite^4.2.4indirect
npm@types/dagre^0.7.53indirect
npm@types/node^24.0.10indirect
npm@vitejs/plugin-vue^6.0.6indirect
npm@vue-flow/background^1.3.2indirect
npm@vue-flow/controls^1.1.3indirect
npm@vue-flow/core^1.48.0indirect
npm@vue-flow/minimap^1.5.4indirect
npm@vue/test-utils^2.4.6indirect
npm@vue/tsconfig^0.7.0indirect
npmansi-to-html^0.7.2indirect
npmconcurrently^10.0.3indirect
npmcross-env^10.1.0indirect
npmdagre^0.8.5indirect
npmelement-plus^2.11.4indirect
npmfast-glob^3.3.3indirect
npmflow-mindmap^0.5.14indirect
npmjsdom^25.0.0indirect
npmmarked^18.0.3indirect
npmmarkstream-vue1.0.3-beta.2indirect
npmmonaco-editor^0.55.1indirect
npmnodemon^3.1.14indirect
npmpinia^3.0.2indirect
npmsass-embedded^1.92.0indirect
npmtailwindcss^4.2.4indirect
npmtypescript~5.7.2indirect
npmunplugin-auto-import^19.2.0indirect
npmunplugin-vue-components^28.5.0indirect
npmvite^8.0.10indirect
npmvite-plugin-svg-icons^2.0.1indirect
npmvitest^3.0.0indirect
npmvue^3.5.13indirect
npmvue-i18n^9.14.5indirect
npmvue-tsc^2.2.8indirect
npmzen-ai-chat-ui^0.1.0-beta.1indirect
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.11.0 — full methodology · metrics wiki.

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