Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 01:12 UTC

canonical / Pebble

Pebble is a lightweight Linux service manager with layered configuration and an HTTP API

GoGPL-3.0★ 202 stars⑂ 74 forkssince Nov 2020View on GitHub ↗
#api#go#service-manager

canonical/Pebble holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Vitality (91/100) and lowest on AI Readiness (56/100). It was last updated 8 days ago. 3 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
3,844 followers2,369 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
Gogithub.com/canonical/pebblev1.32.0-5415 days ago

Metrics by category

Vitality

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

91Excellent · 21% of overall

Development activity

85Excellent
How it's scored
28.8/36Push recency — last push 8 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 163 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year163
human_commit_share—
days_since_last_push8
active_weeks_last_year43

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 54 releases published
36/36Release recency — latest release 14 days ago
27/27Release cadence — a release every ~17 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count54
latest_release_tagv1.32.0-fips
releases_from_tagsno
days_since_latest_release14
mean_days_between_releases17

Community & Adoption

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

61Moderate · 17% of overall

Popularity & adoption

58Moderate
How it's scored
37.4/60Stars — 202 stars
15.5/25Forks — 74 forks
5.3/15Watchers — 10 watchers
Inputs used
forks74
stars202
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

65Good
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges—
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

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

89Excellent · 23% of overall

Maintainer resilience (bus factor)

71Good
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
14.8/22.5Commit distribution — top contributor authored 34% of commits
13.5/13.5Contributor breadth — 48 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor3
contributors_sampled48
top_contributor_share0.343

Issue & PR responsiveness

89Excellent
How it's scored
39.3/42Issue resolution — 94% of issues closed
24.6/30PR acceptance — 551/671 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs551
open_issues15
closed_issues216
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio0.935
closed_unmerged_prs120
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

100Exceptional
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
25/25Owner reach — 3,844 followers of canonical
25/25Track record — 2,369 public repos, account ~6 yr old
Inputs used
followers3,844
owner_typeOrganization
is_verified—
owner_logincanonical
public_repos2,369
account_age_days2,554
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 go
35/35Publish recency — latest publish 15 days ago
20/20Version history — 54 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/canonical/pebble
ecosystemsgo
any_deprecatedno
min_days_since_publish15

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall

Engineering practices

60Moderate
How it's scored
24/24CI workflows — 11 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://ubuntu.com/docs/pebble/
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsapi, go, service-manager
has_wikino
homepagehttps://ubuntu.com/docs/pebble/
docs_sitehttps://ubuntu.com/docs/pebble/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

73Good · 16% of overall

Security posture

73Good
How it's scored
30/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesgo.sum
manifestsdocs/requirements.txt, go.mod
has_codeql_workflowno
has_security_policyyes
has_dependabot_configyes
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

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.

56Moderate · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

Verify loop (build / test / typecheck)

82Excellent
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no data
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — Go (statically typed)
54.5/55Manageable file sizes — 3/353 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes77,309
source_files_sampled353
oversized_source_files3

Machine-readable interfaces

50Moderate
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — docs/_extra/openapi.yaml, docs/specs/openapi.yaml
0/20MCP server — not applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filesdocs/_extra/openapi.yaml, docs/specs/openapi.yaml
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

202GitHub stars
48contributors
163commits, last 12 months
8days since last push
54releases
3bus factor
15open issues
Go, PyPIpackage ecosystems

Data collection warnings

  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Direct dependencies 11
RegistryPackageVersion constraintManifest
Gogithub.com/GehirnInc/cryptv0.0.0-20230320061759-8cc1b52080c5go.mod
Gogithub.com/canonical/go-flagsv0.0.0-20230403090104-105d09a091b8go.mod
Gogithub.com/canonical/x-gov0.0.0-20230522092633-7947a7587f5bgo.mod
Gogithub.com/gorilla/muxv1.8.1go.mod
Gogithub.com/gorilla/websocketv1.5.3go.mod
Gogithub.com/pkg/termv1.1.0go.mod
Gogolang.org/x/sysv0.46.0go.mod
Gogolang.org/x/termv0.44.0go.mod
Gogopkg.in/check.v1v1.0.0-20201130134442-10cb98267c6cgo.mod
Gogopkg.in/tomb.v2v2.0.0-20161208151619-d5d1b5820637go.mod
Gogopkg.in/yaml.v3v3.0.1go.mod
All dependencies 41

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

RegistryPackageVersionRelation
Gogithub.com/canonical/go-flagsv0.0.0-20230403090104-105d09a091b8direct
Gogithub.com/canonical/x-gov0.0.0-20230522092633-7947a7587f5bdirect
Gogithub.com/gehirninc/cryptv0.0.0-20230320061759-8cc1b52080c5direct
Gogithub.com/gorilla/muxv1.8.1direct
Gogithub.com/gorilla/websocketv1.5.3direct
Gogithub.com/pkg/termv1.1.0direct
Gogolang.org/x/sysv0.46.0direct
Gogolang.org/x/termv0.44.0direct
Gogopkg.in/check.v1v1.0.0-20201130134442-10cb98267c6cdirect
Gogopkg.in/tomb.v2v2.0.0-20161208151619-d5d1b5820637direct
Gogopkg.in/yaml.v3v3.0.1direct
Gogithub.com/kr/prettyv0.2.1indirect
Gogithub.com/kr/textv0.2.0indirect
Gogolang.org/x/netv0.56.0indirect
Gogopkg.in/yaml.v2v2.4.0indirect
PyPIcanonical-sphinx—indirect
PyPImyst-parser—indirect
PyPIpackaging—indirect
PyPIrst2html—indirect
PyPIsphinx-autobuild—indirect
PyPIsphinx-config-options—indirect
PyPIsphinx-contributor-listing—indirect
PyPIsphinx-design0.6.1indirect
PyPIsphinx-filtered-toctree—indirect
PyPIsphinx-last-updated-by-git—indirect
PyPIsphinx-llm—indirect
PyPIsphinx-notfound-page—indirect
PyPIsphinx-related-links—indirect
PyPIsphinx-rerediraffe—indirect
PyPIsphinx-reredirects0.1.6indirect
PyPIsphinx-roles—indirect
PyPIsphinx-sitemap—indirect
PyPIsphinx-tabs—indirect
PyPIsphinx-terminal—indirect
PyPIsphinx-ubuntu-images—indirect
PyPIsphinx-youtube-links—indirect
PyPIsphinxcontrib-jquery—indirect
PyPIsphinxcontrib-mermaid—indirect
PyPIsphinxcontrib-svg2pdfconverter—indirect
PyPIsphinxext-opengraph—indirect
PyPIvale—indirect
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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with canonical/Pebble. Read them side by side →

98go-swagger/go-swaggerSwagger 2.0 implementation for goExceptional94digitalocean/godoDigitalOcean Go API clientExceptional99go-gitea/giteaGit with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CDExceptional98SigNoz/signozSigNoz is an open-source, OpenTelemetry-native observability platform for your team and their AI agents. Get logs, metrics, and traces in one tool with features like APM, distributed tracing, log management, infra monitoring, etc. Combined with SigNoz MCP and a native AI teammate (in SigNoz Cloud) it helps you build more resilient apps.Exceptional98pulumi/pulumiPulumi - Infrastructure as Code in any programming language 🚀Exceptional98traefik/traefikThe Cloud Native Application ProxyExceptional

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

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