Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 16:25 UTC

hubblo-org / scaphandre

⚡ Energy consumption metrology agent. Let "scaph" dive and bring back the metrics that will help you make your systems and applications more sustainable !

Rust · CSSApache-2.0★ 2,010 stars⑂ 130 forkssince Oct 2020View on GitHub ↗
KindNetwork serviceLibraryCommand-line toolhow this is determined

hubblo-org/scaphandre holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (68/100) and lowest on Security (38/100). It was last updated 93 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

HubbloOrganization · verified domain
65 followers17 public repossince Sep 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
crates.ioscaphandre1.0.0368982 days ago

Metrics by category

Vitality

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

42Weak · 21% of overall
How it's scored
9.9/36Push recency — last push 93 days ago
4.8/36Commit cadence — 7/52 weeks with commits
11.3/18Commit volume — 17 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year17
human_commit_share1
days_since_last_push93
active_weeks_last_year7
How it's scored
27/27Ships releases — 10 releases published
27/36Release recency — latest release 96 days ago
12.6/27Release cadence — a release every ~227.4 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count10
latest_release_tagv1.0.3
releases_from_tagsno
days_since_latest_release96
mean_days_between_releases227.4

Community & Adoption

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

68Good · 17% of overall
How it's scored
53.6/60Stars — 2,010 stars
17.6/25Forks — 130 forks
7.9/15Watchers — 27 watchers
Inputs used
forks130
stars2,010
watchers27
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
20.9/80Monthly downloads — 36 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesscaphandre
dependents—
ecosystemscrates
total_downloads13,229
monthly_downloads36
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.1/22.5Commit distribution — top contributor authored 86% of commits
13.5/13.5Contributor breadth — 27 contributors
10/10OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled27
top_contributor_share0.861
How it's scored
27.4/42Issue resolution — 65% of issues closed
18.3/30PR acceptance — 108/177 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 11/15 approved changesets -- score normalized to 7
Inputs used
merged_prs108
open_issues73
closed_issues137
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.652
closed_unmerged_prs69
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
13.1/25Owner reach — 65 followers of hubblo-org
21.1/25Track record — 17 public repos, account ~6 yr old
Inputs used
followers65
owner_typeOrganization
is_verifiedyes
owner_loginhubblo-org
public_repos17
account_age_days2,232
How it's scored
25/25Published & resolvable — 1 package(s) on crates
4/35Publish recency — latest publish 982 days ago
20/20Version history — 8 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesscaphandre
ecosystemscrates
any_deprecatedno
min_days_since_publish982

Engineering Quality

Are baseline engineering and documentation practices in place?

55Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 1 out of 12 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://scaphandre.hubblo.org
10/10Repository description
10/10Topics — 20 topics
0/10Wiki
Inputs used
topicsgreenit, rust, rust-lang, energy, energy-consumption, energy-efficiency, energy-monitor, sustainability, electricity, electricity-consumption, electricity-meter, prometheus, watts, wattmeter, qemu, virtual-machines, carbon-footprint, virtual-machine, measure, hacktoberfest
has_wikino
homepage—
docs_sitehttps://scaphandre.hubblo.org
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

38Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 1 out of 12 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-Review — Found 11/15 approved changesets -- score normalized to 7
2.5/2.5Contributors — project has 8 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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not 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
0/7.5Vulnerabilities — 39 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate3.8

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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 89 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.89
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Rust (statically typed)
51.9/55Manageable file sizes — 1/18 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes61,947
source_files_sampled18
oversized_source_files1

Key facts

2,010GitHub stars
27contributors
17commits, last 12 months
93days since last push
10releases
1bus factor
73open issues
crates.iopackage 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

More detail

Star and fork history 0 ★ / 130 ⇿
0Stars
130Forks
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.

025507510012515012752020-122023-112026-10
Major 1Minor 5Patch 4

Each point covers 6 days.

OpenSSF Scorecard 3.8 / 10
3.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-10-21 16:24 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests1 out of 12 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 11/15 approved changesets -- score normalized to 7
10Contributorsproject has 8 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities39 existing vulnerabilities detected
Direct dependencies 20
RegistryPackageVersion constraintManifest
crates.iologgerv0.7Cargo.toml
crates.iolog0.4Cargo.toml
crates.ioclap4.2Cargo.toml
crates.ioregex1.7Cargo.toml
crates.ioriemann_client1.0.0Cargo.toml
crates.iohostname0.3.1Cargo.toml
crates.ioserde1.0Cargo.toml
crates.ioserde_json1.0Cargo.toml
crates.ioordered-float2.0Cargo.toml
crates.iowarp102.0.0Cargo.toml
crates.iotime0.3Cargo.toml
crates.iocolored2.0Cargo.toml
crates.iochrono0.4Cargo.toml
crates.iodocker-sync0.1.2Cargo.toml
crates.iok8s-sync0.2.3Cargo.toml
crates.iohyper0.14Cargo.toml
crates.iotokio1.26.0Cargo.toml
crates.iosysinfo0.28.3Cargo.toml
crates.ioisahc1.7.2Cargo.toml
crates.ioctrlc3.4Cargo.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 — crates.io.