Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 12:56 UTC

epam / ai-dial-client-python

Python client for DIAL API

PythonApache-2.0★ 7 stars⑂ 2 forkssince Oct 2024View on GitHub ↗

epam/ai-dial-client-python holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Sustainability & Governance (90/100) and lowest on Community & Adoption (49/100). It was last updated today. 4 contributors account for most of its recent work.

93
overall / 100
Exceptional

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.

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

Ownership

EPAM SystemsOrganization · verified domain
1,228 followers547 public repossince Mar 2012

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIaidial-client0.18.03,284790 days ago

Metrics by category

Vitality

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

88Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
22.8/36Commit cadence — 33/52 weeks with commits
17.1/18Commit volume — 80 commits in the last year
10/10OpenSSF Scorecard: Maintained — 19 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year80
human_commit_share0.63
days_since_last_push0
active_weeks_last_year33
How it's scored
27/27Ships releases — 23 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~15.1 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count23
latest_release_tag0.18.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases15.1

Community & Adoption

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

49Weak · 17% of overall
How it's scored
12.6/60Stars — 7 stars
0/25Forks — 2 forks
6/15Watchers — 13 watchers
Inputs used
forks2
stars7
watchers13
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
46.9/80Monthly downloads — 3,284 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesaidial-client
dependents—
ecosystemspypi
total_downloads—
monthly_downloads3,284
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?

90Excellent · 23% of overall
How it's scored
43.2/54Bus factor — 4 contributor(s) cover half of all commits
18.2/22.5Commit distribution — top contributor authored 19% of commits
13.5/13.5Contributor breadth — 14 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor4
contributors_sampled14
top_contributor_share0.192
How it's scored
33.6/42Issue resolution — 80% of issues closed
26/30PR acceptance — 98/113 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs98
open_issues7
closed_issues28
prs_merged_7d1
prs_decided_7d1
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.8
closed_unmerged_prs15
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
30/30Ownership backing — organization-owned
20/20Verified domain
22.2/25Owner reach — 1,228 followers of epam
25/25Track record — 547 public repos, account ~14 yr old
Inputs used
followers1,228
owner_typeOrganization
is_verifiedyes
owner_loginepam
public_repos547
account_age_days5,316

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 — 79 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesaidial-client
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

82Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 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 — 30 out of 30 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://dialx.ai
10/10Repository description
10/10Topics — 2 topics
0/10Wiki
Inputs used
topicsai-dial, llm
has_wikino
homepagehttps://dialx.ai
docs_sitehttps://dialx.ai
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

76Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 30 out of 30 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
7.5/7.5Code-Review — all changesets reviewed
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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 — 19 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
3.5/5SAST — SAST tool is not run on all commits -- score normalized to 7
5/5Security-Policy — security policy file 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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

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
advisories0
affected_packages0
assessed_packages42
unassessed_packages0
affected_by_severitynone
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 42 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.

86Excellent · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 55 of 63 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.873
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes2,616
How it's scored
18/18One-command bootstrap — Makefile, noxfile.py
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — aidial_client/py.typed
10/10Reproducible environment — lockfile
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 37 of the last 100 commits are automated dependency updates
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile, noxfile.py
has_devcontainerno
has_linter_configyes
typecheck_configsaidial_client/py.typed
agent_commit_share0.02
toolchain_manifests—
dependency_bot_commit_share0.37
How it's scored
27/45Type-checkable code — Python with type-check config (aidial_client/py.typed)
55/55Manageable file sizes — 0/113 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes18,088
source_files_sampled113
oversized_source_files0

Key facts

7GitHub stars
14contributors
80commits, last 12 months
0days since last push
23releases
4bus factor
7open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:aidial-client@0.18.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
10Releases

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.

111222212026-032026-042026-06
Major 0Minor 6Patch 4
OpenSSF Scorecard 7.0 / 10
7.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-19 12:56 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
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained19 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
7SASTSAST tool is not run on all commits -- score normalized to 7
10Security-Policysecurity policy file 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 4
RegistryPackageVersion constraintManifest
PyPIopenai>=1.1.0,<3pyproject.toml
PyPIhttpx>=0.25.0,<1pyproject.toml
PyPIpydantic>=1.10,<3pyproject.toml
PyPIaiofiles>=0.5.0pyproject.toml
All dependencies 42

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

RegistryPackageVersionRelation
PyPIaiofiles24.1.0direct
PyPIhttpx0.25.2direct
PyPIopenai1.51.0direct
PyPIpydantic2.8.2direct
PyPIannotated-types0.7.0indirect
PyPIanyio4.15.1indirect
PyPIargcomplete3.4.0indirect
PyPIcertifi2024.7.4indirect
PyPIcfgv3.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcolorlog6.8.2indirect
PyPIcoverage7.6.1indirect
PyPIdistlib0.3.8indirect
PyPIdistro1.9.0indirect
PyPIexceptiongroup1.2.2indirect
PyPIfilelock3.32.7indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIidentify2.6.18indirect
PyPIidna3.15indirect
PyPIiniconfig2.0.0indirect
PyPIjiter0.5.0indirect
PyPInodeenv1.9.1indirect
PyPInox2024.4.15indirect
PyPIpackaging24.1indirect
PyPIplatformdirs4.2.2indirect
PyPIpluggy1.5.0indirect
PyPIpre-commit4.5.1indirect
PyPIpydantic-core2.20.1indirect
PyPIpygments2.20.0indirect
PyPIpyright1.1.385indirect
PyPIpytest9.0.3indirect
PyPIpytest-asyncio0.21.2indirect
PyPIpytest-cov5.0.0indirect
PyPIpython-discovery1.6.1indirect
PyPIpyyaml6.0.3indirect
PyPIruff0.12.11indirect
PyPIsniffio1.3.1indirect
PyPItomli2.0.1indirect
PyPItqdm4.66.5indirect
PyPItyping-extensions4.16.0indirect
PyPIvirtualenv21.7.13indirect
Dependency advisories 0

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

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