Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-16 21:57 UTC

canonical / craft-providers

Python interfaces for instantiating and executing builds for a variety of target environments.

PythonLGPL-3.0★ 9 stars⑂ 39 forkssince Jan 2021View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

canonical/craft-providers holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on AI Readiness (93/100) and lowest on Community & Adoption (51/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

CanonicalOrganization · verified domain
4,258 followers2,581 public repossince Jul 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIcraft-providers3.8.127,527764 days ago

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 recency — last push 2 days ago
33.2/36Commit cadence — 48/52 weeks with commits
18/18Commit volume — 255 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year255
human_commit_share0.67
days_since_last_push2
active_weeks_last_year48
How it's scored
27/27Ships releases — 75 releases published
36/36Release recency — latest release 4 days ago
19.8/27Release cadence — a release every ~47.8 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count75
latest_release_tag3.8.1
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases47.8

Community & Adoption

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

51Moderate · 17% of overall
How it's scored
14.6/60Stars — 9 stars
13.2/25Forks — 39 forks
0/15Watchers — 2 watchers
Inputs used
forks39
stars9
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (LGPL-3.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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes

Sustainability & Governance

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

84Excellent · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.3/22.5Commit distribution — top contributor authored 36% of commits
13.5/13.5Contributor breadth — 35 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled35
top_contributor_share0.363
How it's scored
26.4/42Issue resolution — 63% of issues closed
24.9/30PR acceptance — 695/839 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs695
open_issues67
closed_issues113
prs_merged_7d3
prs_decided_7d3
prs_merged_30d6
prs_decided_30d7
issue_closed_ratio0.628
closed_unmerged_prs144
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 4,258 followers of canonical
25/25Track record — 2,581 public repos, account ~7 yr old
Inputs used
followers4,258
owner_typeOrganization
is_verifiedyes
owner_logincanonical
public_repos2,581
account_age_days2,678

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 4 days ago
20/20Version history — 76 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescraft-providers
ecosystemspypi
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

87Excellent · 19% of overall
How it's scored
24/24CI workflows — 8 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff], [tool.isort])
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 10 out of 15 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://canonical-craft-providers.readthedocs-hosted.com
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://canonical-craft-providers.readthedocs-hosted.com
docs_sitehttps://canonical-craft-providers.readthedocs-hosted.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1.5/2.5CI-Tests — 10 out of 15 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 5 contributing companies or organizations
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 6 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
4.5/5SAST — SAST tool is not run on all commits -- score normalized to 9
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
3.8/7.5Vulnerabilities — 5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate6.6

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.

93Exceptional · 4% of overall
How it's scored
45/45Agent instructions — .github/instructions/core-directive.instructions.md, .github/instructions/documentation-rtd.instructions.md, .github/instructions/documentation.instructions.md, .github/instructions/instructions.instructions.md, .github/instructions/python-code-commenting.instructions.md, .github/instructions/starcraft-docs-meta.instructions.md, .github/instructions/starcraft-docs-style.instructions.md, AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://canonical-craft-providers.readthedocs-hosted.com/llms.txt)
40/40Legible commit history — 67 of 67 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://canonical-craft-providers.readthedocs-hosted.com/llms.txt
legible_history_share1
agent_instruction_files.github/instructions/core-directive.instructions.md, .github/instructions/documentation-rtd.instructions.md, .github/instructions/documentation.instructions.md, .github/instructions/instructions.instructions.md, .github/instructions/python-code-commenting.instructions.md, .github/instructions/starcraft-docs-meta.instructions.md, .github/instructions/starcraft-docs-style.instructions.md, AGENTS.md
agent_instruction_max_bytes13,591
How it's scored
18/18One-command bootstrap — Makefile, docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff], [tool.isort])
11/11Static type checking — craft_providers/py.typed
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 15 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 33 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile, docs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configscraft_providers/py.typed
agent_commit_share0.15
toolchain_manifests—
dependency_bot_commit_share0.33
How it's scored
27/45Type-checkable code — Python with type-check config (craft_providers/py.typed)
54.1/55Manageable file sizes — 2/120 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes75,607
source_files_sampled120
oversized_source_files2

Key facts

9GitHub stars
35contributors
255commits, last 12 months
2days since last push
75releases
2bus factor
67open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index pypi:craft-providers@3.8.1; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 39 ⇿
0Stars
39Forks
74Releases

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.

0102030403822021-022023-122026-11
Major 4Minor 36Patch 34

Each point covers 6 days.

OpenSSF Scorecard 6.6 / 10
6.6aggregate

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-11-16 21:56 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
6CI-Tests10 out of 15 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
9SASTSAST tool is not run on all commits -- score normalized to 9
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
5Vulnerabilities5 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
PyPIpackaging>=14.1pyproject.toml
PyPIpydantic~=2.4pyproject.toml
PyPIpylxd>=2.3.5pyproject.toml
PyPIpyyaml—pyproject.toml
PyPIrequests>=2.31pyproject.toml
PyPIrequests_unixsocket2>=0.4.0pyproject.toml
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.