Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-04 15:03 UTC

bim-ba / ycli

Yandex 360 toolkit — Tracker, Wiki & Forms via CLI, MCP server, Python SDK & Claude Code plugin ✨

PythonMIT★ 3 stars⑂ 3 forkssince Jun 2026View on GitHub ↗
KindCommand-line toolLibraryMCP serverhow this is determined

bim-ba/ycli holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (96/100) and lowest on Community & Adoption (47/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

savaPersonal account
4 followers6 public repossince Apr 2021

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
PyPIyandex-cli0.60.0-800 days agoclifastmcpformsmcpsdktrackertyperwikiyandexyandex-360

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
6.2/36Commit cadence — 9/52 weeks with commits
18/18Commit volume — 346 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year346
human_commit_share1
days_since_last_push0
active_weeks_last_year9
How it's scored
27/27Ships releases — 81 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~0.1 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count81
latest_release_tagv0.60.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases0.1

Community & Adoption

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

47Weak · 17% of overall
How it's scored
4.9/60Stars — 3 stars
2.5/25Forks — 3 forks
0/15Watchers — 0 watchers
Inputs used
forks3
stars3
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges7
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes

Sustainability & Governance

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

50Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.3/22.5Commit distribution — top contributor authored 98% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.985
How it's scored
27.7/42Issue resolution — 66% of issues closed
29.1/30PR acceptance — 192/198 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_prs192
open_issues32
closed_issues62
prs_merged_7d59
prs_decided_7d60
prs_merged_30d59
prs_decided_30d60
issue_closed_ratio0.66
closed_unmerged_prs6
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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
5/25Owner reach — 4 followers of bim-ba
17.1/25Track record — 6 public repos, account ~5 yr old
Inputs used
followers4
owner_typeUser
is_verified—
owner_loginbim-ba
public_repos6
account_age_days2,008
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 — 80 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesyandex-cli
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

96Exceptional · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 17 out of 17 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://bim-ba.github.io/ycli/
10/10Repository description
10/10Topics — 14 topics
10/10Wiki
Inputs used
topicsai-agents, claude-code, cli, fastmcp, mcp, mcp-server, python, sdk, typer, yandex, yandex-360, yandex-tracker, yandex-wiki, yandex-forms
has_wikiyes
homepagehttps://bim-ba.github.io/ycli/
docs_sitehttps://bim-ba.github.io/ycli/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

68Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 17 out of 17 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 30 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
4/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
1.5/7.5Vulnerabilities — 8 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate6

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories16
affected_packages3
assessed_packages122
unassessed_packages0
affected_by_severitycritical 1, high 1, moderate 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 122 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

88Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://bim-ba.github.io/ycli/llms.txt)
40/40Legible commit history — 75 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://bim-ba.github.io/ycli/llms.txt
legible_history_share0.75
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes10,317
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — src/ycli/py.typed
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 48 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
8/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configssrc/ycli/py.typed
agent_commit_share0.48
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (src/ycli/py.typed)
54.9/55Manageable file sizes — 1/772 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes71,270
source_files_sampled772
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

3GitHub stars
3contributors
346commits, last 12 months
0days since last push
81releases
1bus factor
32open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'yandex-cli' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
  • Could not fetch pypi package 'yandex-360-mcpb' from its registry
  • deps.dev does not index pypi:yandex-cli@0.60.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 3 ⇿
0Stars
3Forks
1Releases

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.

12233312026-082026-082026-09
Major 0Minor 1Patch 0
OpenSSF Scorecard 6.0 / 10
6.0aggregate

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-04 15:02 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests17 out of 17 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 30 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
2Vulnerabilities8 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
PyPIyandex-cli==0.60.0mcpb/pyproject.toml
PyPIhttpx2>=2.13.1pyproject.toml
PyPIplatformdirs>=4.10.0pyproject.toml
PyPIpydantic>=2.13.4pyproject.toml
PyPIpydantic-settings>=2.14.2pyproject.toml
PyPIpython-dotenv>=1.2.2pyproject.toml
PyPIpyyaml>=6.0.3pyproject.toml
PyPIrich>=15.0.0pyproject.toml
PyPIstamina>=26.1.0pyproject.toml
PyPItyper>=0.26.8pyproject.toml
All dependencies 122

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

RegistryPackageVersionRelation
PyPIhttpx22.13.1direct
PyPIplatformdirs4.10.0direct
PyPIpydantic2.13.4direct
PyPIpydantic-settings2.14.2direct
PyPIpython-dotenv1.2.2direct
PyPIpyyaml6.0.3direct
PyPIrich15.0.0direct
PyPIstamina26.1.0direct
PyPItyper0.26.8direct
PyPIyandex-cli0.60.0direct
PyPIaiofile3.11.1indirect
PyPIannotated-doc0.0.4indirect
PyPIannotated-types0.7.0indirect
PyPIanyio4.14.1indirect
PyPIattrs26.1.0indirect
PyPIauthlib1.7.2indirect
PyPIbeartype0.22.9indirect
PyPIcachetools7.1.4indirect
PyPIcaio0.9.25indirect
PyPIcffi2.0.0indirect
PyPIcfgv3.5.0indirect
PyPIclick8.4.2indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.14.3indirect
PyPIcryptography49.0.0indirect
PyPIcyclopts4.19.0indirect
PyPIdeepmerge3.0.1indirect
PyPIdistlib0.4.3indirect
PyPIdnspython2.8.0indirect
PyPIdocstring-parser0.18.0indirect
PyPIemail-validator2.3.0indirect
PyPIexceptiongroup1.3.1indirect
PyPIexecnet2.1.2indirect
PyPIfastmcp4.0.10indirect
PyPIfastmcp-slim4.0.10indirect
PyPIfilelock3.29.4indirect
PyPIghp-import2.1.0indirect
PyPIgriffelib2.1.0indirect
PyPIgrimp3.14indirect
PyPIh110.16.0indirect
PyPIhttpcore22.13.1indirect
PyPIhttpx2-jsfetch1.0indirect
PyPIidentify2.6.19indirect
PyPIidna3.18indirect
PyPIimport-linter2.12indirect
PyPIiniconfig2.3.0indirect
PyPIjaraco-classes3.4.0indirect
PyPIjaraco-context6.1.2indirect
PyPIjaraco-functools4.5.0indirect
PyPIjeepney0.9.0indirect
PyPIjinja23.1.6indirect
PyPIjmespath1.1.0indirect
PyPIjoserfc1.7.1indirect
PyPIjsonref1.1.0indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-path0.5.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPIkeyring25.7.0indirect
PyPIlazy-object-proxy1.12.0indirect
PyPImarkdown3.11indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.4indirect
PyPImcp2.2.0indirect
PyPImcp-types2.2.0indirect
PyPImdurl0.1.2indirect
PyPImergedeep1.3.4indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-autorefs1.4.4indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImkdocstrings1.0.6indirect
PyPImkdocstrings-python2.0.9indirect
PyPImore-itertools11.1.0indirect
PyPInodeenv1.10.0indirect
PyPIopenapi-pydantic0.5.1indirect
PyPIopenapi-schema-validator0.9.0indirect
PyPIopenapi-spec-validator0.9.0indirect
PyPIopentelemetry-api1.43.0indirect
PyPIpackaging26.2indirect
PyPIpathable0.6.0indirect
PyPIpathspec1.1.1indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.6.0indirect
PyPIpy-key-value-aio0.4.5indirect
PyPIpycparser3.0indirect
PyPIpydantic-core2.46.4indirect
PyPIpygments2.20.0indirect
PyPIpyjwt2.15.1indirect
PyPIpymdown-extensions12.1indirect
PyPIpyperclip1.11.0indirect
PyPIpytest9.1.1indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-xdist3.8.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-discovery1.4.2indirect
PyPIpython-multipart0.0.32indirect
PyPIpywin32312indirect
PyPIpywin32-ctypes0.2.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIreferencing0.37.0indirect
PyPIrfc3339-validator0.1.4indirect
PyPIrich-rst2.0.2indirect
PyPIrpds-py2026.5.1indirect
PyPIruff0.15.20indirect
PyPIsecretstorage3.5.0indirect
PyPIshellingham1.5.4indirect
PyPIsix1.17.0indirect
PyPIsse-starlette3.4.5indirect
PyPIstarlette1.3.1indirect
PyPItenacity9.1.4indirect
PyPItomli2.4.1indirect
PyPItruststore0.10.4indirect
PyPIty0.0.55indirect
PyPItyping-extensions4.15.0indirect
PyPItyping-inspection0.4.2indirect
PyPIuncalled-for0.4.0indirect
PyPIuvicorn0.49.0indirect
PyPIvirtualenv21.5.1indirect
PyPIwatchdog6.0.0indirect
PyPIwatchfiles1.2.0indirect
PyPIwebsockets16.0indirect
PyPIzensical0.0.67indirect
Dependency advisories 3

This repository publishes no package the index resolves, so its own dependency graph was assessed — 122 packages, which also include development and test pins that never ship: 3 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
anyio4.14.1indirectcritical64.14.2
virtualenv21.5.1indirecthigh821.7.13
cryptography49.0.0indirectmoderate250.0.0

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 statistics — PyPI.