Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-11 07:27 UTC

smithy-lang / smithy-python

Smithy code generators and core modules for Python (in development)

Python · JavaApache-2.0★ 83 stars⑂ 31 forkssince Feb 2021View on GitHub ↗

smithy-lang/smithy-python holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Security (82/100) and lowest on Engineering Quality (57/100). It was last updated today. A single contributor accounts for most of its recent work.

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.

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)

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

Ownership

smithy-langOrganization

111 followers23 public repossince May 2023

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
PyPI	smithy-xml	0.1.0	-	1	125 days ago	sdk smithy xml
PyPI	smithy-core	0.7.0	486,496	10	10 days ago	sdk smithy
PyPI	smithy-http	0.4.3	474,916	10	10 days ago	http sdk smithy
PyPI	smithy-json	0.2.3	474,267	6	49 days ago	json sdk smithy
PyPI	aws-sdk-signers	0.3.0	449,305	6	97 days ago	amazon aws http sdk signing sigv4
PyPI	smithy-aws-core	0.8.0	-	12	10 days ago	amazon aws sdk smithy
PyPI	smithy-aws-event-stream	0.3.0	441,154	6	97 days ago	amazon aws eventstream sdk smithy

Metrics by category

Vitality

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

60Moderate · 21% of overall

Development activity

99Exceptional

How it's scored

36/36	Push recency — last push 0 days ago
35.3/36	Commit cadence — 51/52 weeks with commits
18/18	Commit volume — 226 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	226
human_commit_share	0.6
days_since_last_push	0
active_weeks_last_year	51

Release discipline

1Critical

How it's scored

0/27	Ships releases — no releases published
0/36	Release recency — no releases
0/27	Release cadence — no releases
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count

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?

76Good · 17% of overall

Popularity & adoption

47Weak

How it's scored

31/60	Stars — 83 stars
12.3/25	Forks — 31 forks
3.3/15	Watchers — 5 watchers

Inputs used

forks	31
stars	83
watchers	5
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

92Excellent

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (Apache-2.0)
18/18	CONTRIBUTING guide
13.5/13.5	Code of conduct
0/7.2	Issue template
6.3/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	0
has_contributing	yes
has_issue_template	no
has_code_of_conduct	yes
readme_badge_services	—
has_pull_request_template	yes

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 2,326,138 downloads/month across pypi
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	smithy-xml, smithy-core, smithy-http, smithy-json, aws-sdk-signers, smithy-aws-core, smithy-aws-event-stream
dependents	—
ecosystems	pypi
total_downloads	—
monthly_downloads	2,326,138
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?

68Good · 23% of overall

Maintainer resilience (bus factor)

42Weak

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
9/22.5	Commit distribution — top contributor authored 60% of commits
13.5/13.5	Contributor breadth — 20 contributors
10/10	OpenSSF Scorecard: Contributors — project has 9 contributing companies or organizations

Inputs used

bus_factor	1
contributors_sampled	20
top_contributor_share	0.599

Issue & PR responsiveness

67Good

How it's scored

18.5/42	Issue resolution — 44% of issues closed
28/30	PR acceptance — 674/722 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
12/15	OpenSSF Scorecard: Code-Review — Found 15/18 approved changesets -- score normalized to 8

Inputs used

merged_prs	674
open_issues	14
closed_issues	11
prs_merged_7d	1
prs_decided_7d	2
prs_merged_30d	3
prs_decided_30d	5
issue_closed_ratio	0.44
closed_unmerged_prs	48
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

76Good

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain — verified-domain status not read for this organization
14.7/25	Owner reach — 111 followers of smithy-lang
16.5/25	Track record — 23 public repos, account ~3 yr old

Inputs used

followers	111
owner_type	Organization
is_verified	—
owner_login	smithy-lang
public_repos	23
account_age_days	1,182

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 7 package(s) on pypi
35/35	Publish recency — latest publish 10 days ago
20/20	Version history — 12 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	smithy-xml, smithy-core, smithy-http, smithy-json, aws-sdk-signers, smithy-aws-core, smithy-aws-event-stream
ecosystems	pypi
any_deprecated	no
min_days_since_publish	10

Engineering Quality

Are baseline engineering and documentation practices in place?

57Moderate · 19% of overall

Engineering practices

68Good

How it's scored

24/24	CI workflows — 4 workflow(s)
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
20/20	OpenSSF Scorecard: CI-Tests — 27 out of 27 merged PRs checked by a CI test -- score normalized to 10

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

40Weak

How it's scored

30/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
0/10	Topics
0/10	Wiki

Inputs used

topics	—
has_wiki	no
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	no
has_description	yes

Security

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

82Excellent · 16% of overall

Security posture

78Good

How it's scored

6.8/7.5	Binary-Artifacts — binaries present in source code
4.5/7.5	Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5	CI-Tests — 27 out of 27 merged PRs checked by a CI test -- score normalized to 10
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6/7.5	Code-Review — Found 15/18 approved changesets -- score normalized to 8
2.5/2.5	Contributors — project has 9 contributing companies or organizations
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
7.5/7.5	Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5	Packaging — no data
5/5	Pinned-Dependencies — all dependencies are pinned
5/5	SAST — SAST tool is run on all commits
5/5	Security-Policy — security policy file detected
0/7.5	Signed-Releases — no data
7.5/7.5	Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5	Vulnerabilities — 12 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	16
scorecard_version	v5.5.0
checks_inconclusive	2
scorecard_aggregate	7.8

Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25	Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	0
affected_packages	0
assessed_packages	1
unassessed_packages	0
affected_by_severity	none
direct_affected_packages	0

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:smithy-xml@0.1.0 runtime dependency closure — what installing the published package pulls in — 1 packages. 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.

69Good · 4% of overall

Agent context & guidance

33At Risk

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
32.9/40	Legible commit history — 37 of 60 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.617
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

79Good

How it's scored

18/18	One-command bootstrap — Makefile
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — packages/aws-sdk-signers/src/aws_sdk_signers/py.typed, packages/smithy-aws-core/src/smithy_aws_core/py.typed, packages/smithy-aws-event-stream/src/smithy_aws_event_stream/py.typed, packages/smithy-aws-event-stream/tests/py.typed, packages/smithy-core/src/smithy_core/py.typed, packages/smithy-core/tests/py.typed, packages/smithy-http/src/smithy_http/py.typed, packages/smithy-http/tests/py.typed, packages/smithy-json/src/smithy_json/py.typed, packages/smithy-xml/src/smithy_xml/py.typed
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
8/8	Automated maintenance — 40 of the last 100 commits are automated dependency updates
10/10	OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned

Inputs used

has_nix	no
has_tests	yes
lockfiles	uv.lock
has_dockerfile	no
typed_language	no
bootstrap_files	Makefile
has_devcontainer	no
has_linter_config	no
typecheck_configs	packages/aws-sdk-signers/src/aws_sdk_signers/py.typed, packages/smithy-aws-core/src/smithy_aws_core/py.typed, packages/smithy-aws-event-stream/src/smithy_aws_event_stream/py.typed, packages/smithy-aws-event-stream/tests/py.typed, packages/smithy-core/src/smithy_core/py.typed, packages/smithy-core/tests/py.typed, packages/smithy-http/src/smithy_http/py.typed, packages/smithy-http/tests/py.typed, packages/smithy-json/src/smithy_json/py.typed, packages/smithy-xml/src/smithy_xml/py.typed
agent_commit_share	0
toolchain_manifests	codegen/aws/core/build.gradle.kts, codegen/build.gradle.kts, codegen/buildSrc/build.gradle.kts, codegen/core/build.gradle.kts, codegen/plugins/build.gradle.kts, codegen/plugins/types/build.gradle.kts, codegen/protocol-test/build.gradle.kts
dependency_bot_commit_share	0.4

Code legibility for models

82Excellent

How it's scored

27/45

Type-checkable code — Python with type-check config (packages/aws-sdk-signers/src/aws_sdk_signers/py.typed, packages/smithy-aws-core/src/smithy_aws_core/py.typed, packages/smithy-aws-event-stream/src/smithy_aws_event_stream/py.typed, packages/smithy-aws-event-stream/tests/py.typed, packages/smithy-core/src/smithy_core/py.typed, packages/smithy-core/tests/py.typed, packages/smithy-http/src/smithy_http/py.typed, packages/smithy-http/tests/py.typed, packages/smithy-json/src/smithy_json/py.typed, packages/smithy-xml/src/smithy_xml/py.typed)

54.8/55

Manageable file sizes — 1/290 source files over 60KB

Inputs used

primary_language	Python
largest_source_bytes	70,827
source_files_sampled	290
oversized_source_files	1

Machine-readable interfaces

100Exceptional

How it's scored

0/40	API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20	MCP server — not applicable to this kind of software
40/40	Runnable examples — examples

Inputs used

example_dirs	examples
has_mcp_signal	no
api_schema_files	—
interfaces_expected_of	—

Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

83GitHub stars

20contributors

226commits, last 12 months

0days since last push

0releases

1bus factor

14open issues

Maven, PyPIpackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
Could not fetch pypi package 'smithy-python' from its registry

More detail

Star and fork history 0 ★ / 31 ⇿

0Stars

31Forks

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.

Each point covers 3 days.

OpenSSF Scorecard 7.8 / 10

7.8aggregate

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-08-11 07:27 UTC

9	Binary-Artifacts	binaries present in source code
6	Branch-Protection	branch protection is not maximal on development and all release branches
10	CI-Tests	27 out of 27 merged PRs checked by a CI test -- score normalized to 10
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
8	Code-Review	Found 15/18 approved changesets -- score normalized to 8
10	Contributors	project has 9 contributing companies or organizations
10	Dangerous-Workflow	no dangerous workflow patterns detected
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/a	Packaging	packaging workflow not detected
10	Pinned-Dependencies	all dependencies are pinned
10	SAST	SAST tool is run on all commits
10	Security-Policy	security policy file detected
n/a	Signed-Releases	no releases found
10	Token-Permissions	GitHub workflow tokens follow principle of least privilege
0	Vulnerabilities	12 existing vulnerabilities detected

Direct dependencies 8

Registry	Package	Version constraint	Manifest
PyPI	smithy-core	`~=0.7.0`	packages/smithy-aws-core/pyproject.toml
PyPI	smithy-http	`~=0.4.0`	packages/smithy-aws-core/pyproject.toml
PyPI	aws-sdk-signers	`~=0.3.0`	packages/smithy-aws-core/pyproject.toml
PyPI	smithy-core	`—`	packages/smithy-aws-event-stream/pyproject.toml
PyPI	smithy-core	`—`	packages/smithy-http/pyproject.toml
PyPI	ijson	`>=3.3.0`	packages/smithy-json/pyproject.toml
PyPI	smithy-core	`—`	packages/smithy-json/pyproject.toml
PyPI	smithy-core	`—`	packages/smithy-xml/pyproject.toml

All dependencies 40

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

Registry	Package	Version	Relation
PyPI	aws-sdk-signers	`—`	direct
PyPI	ijson	`—`	direct
PyPI	ijson	`3.3.0`	direct
PyPI	smithy-core	`—`	direct
PyPI	smithy-http	`—`	direct
PyPI	aiohappyeyeballs	`2.6.1`	indirect
PyPI	aiohttp	`—`	indirect
PyPI	aiohttp	`3.14.0`	indirect
PyPI	aiosignal	`1.4.0`	indirect
PyPI	attrs	`25.3.0`	indirect
PyPI	awscrt	`—`	indirect
PyPI	awscrt	`0.32.0`	indirect
PyPI	colorama	`0.4.6`	indirect
PyPI	coverage	`7.12.0`	indirect
PyPI	freezegun	`1.5.5`	indirect
PyPI	frozenlist	`1.6.0`	indirect
PyPI	idna	`3.15`	indirect
PyPI	iniconfig	`2.1.0`	indirect
PyPI	jinja2	`3.1.6`	indirect
PyPI	markupsafe	`3.0.2`	indirect
PyPI	multidict	`6.4.3`	indirect
PyPI	nodeenv	`1.9.1`	indirect
PyPI	packaging	`25.0`	indirect
PyPI	pluggy	`1.5.0`	indirect
PyPI	propcache	`0.3.1`	indirect
PyPI	pygments	`2.19.2`	indirect
PyPI	pyright	`1.1.406`	indirect
PyPI	pytest	`9.0.3`	indirect
PyPI	pytest-asyncio	`1.3.0`	indirect
PyPI	pytest-cov	`7.0.0`	indirect
PyPI	python-dateutil	`2.9.0.post0`	indirect
PyPI	ruff	`0.15.22`	indirect
PyPI	six	`1.17.0`	indirect
PyPI	smithy-aws-event-stream	`—`	indirect
PyPI	smithy-json	`—`	indirect
PyPI	smithy-python	`0.1.0`	indirect
PyPI	smithy-xml	`—`	indirect
PyPI	typing-extensions	`—`	indirect
PyPI	typing-extensions	`4.13.2`	indirect
PyPI	yarl	`1.20.0`	indirect

Dependency advisories 0

Installing pypi:smithy-xml@0.1.0 pulls in 1 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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.

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.31.0 — full methodology · metrics wiki.

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

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records