Public recordExcellent
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 21:16 UTC
provide-io / provide-telemetry
Unified telemetry library for the provide.io ecosystem — structured logging, distributed tracing, and metrics
provide-io/provide-telemetry holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (92/100) and lowest on Community & Adoption (40/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.
86
overall / 100Software 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.
86
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 72 is calibrated to 86 on the published index scale (record calibration 2026-08-02).
Ownership
provide.ioOrganization · verified domain
2 followers24 public repossince Mar 2024
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 | provide-telemetry | 0.11.0 | 3,453 | 20 | 6 days ago | telemetryobservabilityopentelemetrystructlogoteltracingmetricslogging |
| Go | github.com/provide-io/provide-telemetry/go | v0.11.0 | - | 18 | 6 days ago | — |
| crates.io | provide-telemetry | 0.11.0 | 140 | 15 | 6 days ago | telemetryobservabilityopentelemetryotlp |
| npm | @provide-io/telemetry | 0.11.0 | 677 | 20 | 6 days ago | telemetryobservabilityopentelemetryoteltracingmetricsloggingstructlogpinow3c-traceparent |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
87
Development activity
80Excellent
How it's scored
| 36/36 | Push recency — last push 6 days ago |
| 15.9/36 | Commit cadence — 23/52 weeks with commits |
| 18/18 | Commit volume — 1,241 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 1,241 |
| human_commit_share | 1 |
| days_since_last_push | 6 |
| active_weeks_last_year | 23 |
Release discipline
98Exceptional
How it's scored
| 27/27 | Ships releases — 20 releases published |
| 36/36 | Release recency — latest release 6 days ago |
| 27/27 | Release cadence — a release every ~6.4 days |
| 8/10 | OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts. |
Inputs used
| releases_count | 20 |
| latest_release_tag | v0.11.0 |
| releases_from_tags | no |
| days_since_latest_release | 6 |
| mean_days_between_releases | 6.4 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
40
Popularity & adoption
1Critical
How it's scored
| 0/60 | Stars — 0 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 0 |
| stars | 0 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
71Good
How it's scored
| 22.5/22.5 | README |
| 16.9/22.5 | License — license file present, not a recognized license |
| 18/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 6.3/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | no |
| readme_badges | 5 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | github.com |
| has_pull_request_template | yes |
Ecosystem adoption (downloads)
60Moderate
How it's scored
| 48.4/80 | Monthly downloads — 4,270 downloads/month across crates, go, npm, pypi |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | provide-telemetry, github.com/provide-io/provide-telemetry/go, provide-telemetry, @provide-io/telemetry |
| dependents | — |
| ecosystems | crates, go, npm, pypi |
| total_downloads | 537 |
| monthly_downloads | 4,270 |
| 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?
58
Maintainer resilience (bus factor)
16Critical
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0/22.5 | Commit distribution — top contributor authored 100% of commits |
| 1.4/13.5 | Contributor breadth — 1 contributors |
| 6/10 | OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 1 |
| top_contributor_share | 1 |
How it's scored
| 37/42 | Issue resolution — 88% of issues closed |
| 19.3/30 | PR acceptance — 54/84 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/25 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 54 |
| open_issues | 2 |
| closed_issues | 15 |
| prs_merged_7d | 5 |
| prs_decided_7d | 5 |
| prs_merged_30d | 5 |
| prs_decided_30d | 6 |
| issue_closed_ratio | 0.882 |
| closed_unmerged_prs | 30 |
| 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
69Good
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 20/20 | Verified domain |
| 3.4/25 | Owner reach — 2 followers of provide-io |
| 15.4/25 | Track record — 24 public repos, account ~2 yr old |
Inputs used
| followers | 2 |
| owner_type | Organization |
| is_verified | yes |
| owner_login | provide-io |
| public_repos | 24 |
| account_age_days | 954 |
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 4 package(s) on crates, go, npm, pypi |
| 35/35 | Publish recency — latest publish 6 days ago |
| 20/20 | Version history — 20 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | provide-telemetry, github.com/provide-io/provide-telemetry/go, provide-telemetry, @provide-io/telemetry |
| ecosystems | crates, go, npm, pypi |
| any_deprecated | no |
| min_days_since_publish | 6 |
Engineering Quality
Are baseline engineering and documentation practices in place?
92
Engineering practices
94Exceptional
How it's scored
| 24/24 | CI workflows — 13 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — .golangci.yml, eslint.config.js, pyproject.toml ([tool.ruff]) |
| 9.6/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 22 out of 22 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 | yes |
| has_precommit_config | yes |
Documentation
90Excellent
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://github.com/provide-io/provide-telemetry |
| 10/10 | Repository description |
| 0/10 | Topics |
| 10/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | yes |
| homepage | https://github.com/provide-io/provide-telemetry |
| docs_site | https://github.com/provide-io/provide-telemetry |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
80
Security posture
75Good
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 2.5/2.5 | CI-Tests — 22 out of 22 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 |
| 0/7.5 | Code-Review — Found 0/25 approved changesets -- score normalized to 0 |
| 1.5/2.5 | Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 5/5 | Fuzzing — project is fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 |
| 5/5 | Packaging — packaging workflow detected |
| 4.5/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9 |
| 5/5 | SAST — SAST tool is run on all commits |
| 5/5 | Security-Policy — security policy file detected |
| 6/7.5 | Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts. |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 3.8/7.5 | Vulnerabilities — 5 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 17 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 1 |
| scorecard_aggregate | 7.5 |
Excluded from scoring (no data or not applicable): Branch-Protection. 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:provide-telemetry@0.11.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.
87
Agent context & guidance
85Excellent
How it's scored
| 45/45 | Agent instructions — CLAUDE.md |
| 0/15 | Machine-readable docs (llms.txt) |
| 40/40 | Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 1 |
| agent_instruction_files | CLAUDE.md |
| agent_instruction_max_bytes | 16,291 |
Verify loop (build / test / typecheck)
86Excellent
How it's scored
| 18/18 | One-command bootstrap — Makefile, go/Makefile |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — .golangci.yml, eslint.config.js, pyproject.toml ([tool.ruff]) |
| 11/11 | Static type checking — src/provide/telemetry/py.typed, typescript/examples/tsconfig.json, typescript/tsconfig.json |
| 10/10 | Reproducible environment — Dockerfile, lockfile |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 5/8 | Automated maintenance — dependency automation configured, none observed in the sampled commits |
| 9/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | Cargo.lock, go.sum, package-lock.json, uv.lock |
| has_dockerfile | yes |
| typed_language | no |
| bootstrap_files | Makefile, go/Makefile |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | src/provide/telemetry/py.typed, typescript/examples/tsconfig.json, typescript/tsconfig.json |
| agent_commit_share | 0 |
| toolchain_manifests | csharp/consumer/Provide.Telemetry.ConsumerSmoke/Provide.Telemetry.ConsumerSmoke.csproj, csharp/consumer/Provide.Telemetry.CoreConsumer/Provide.Telemetry.CoreConsumer.csproj, csharp/consumer/Provide.Telemetry.OpenTelemetryConsumer/Provide.Telemetry.OpenTelemetryConsumer.csproj, csharp/examples/openobserve/01_emit_all_signals/EmitAllSignals.csproj, csharp/examples/telemetry/01_basic_telemetry/BasicTelemetry.csproj, csharp/examples/telemetry/02_w3c_propagation/W3cPropagation.csproj, csharp/examples/telemetry/15_prometheus_metrics/PrometheusScrape.csproj, csharp/perf/Provide.Telemetry.Perf/Provide.Telemetry.Perf.csproj, csharp/probes/ConfigProbe/ConfigProbe.csproj, csharp/probes/ContractProbe/ContractProbe.csproj, csharp/probes/EmitLog/EmitLog.csproj, csharp/probes/PrometheusPushProbe/PrometheusPushProbe.csproj, csharp/probes/PrometheusScrapeProbe/PrometheusScrapeProbe.csproj, csharp/probes/RuntimeProbe/RuntimeProbe.csproj, csharp/src/Provide.Telemetry.OpenTelemetry/Provide.Telemetry.OpenTelemetry.csproj, csharp/src/Provide.Telemetry/Provide.Telemetry.csproj, csharp/tests/Provide.Telemetry.OpenTelemetry.Tests/Provide.Telemetry.OpenTelemetry.Tests.csproj, csharp/tests/Provide.Telemetry.Tests/Provide.Telemetry.Tests.csproj, go/cmd/e2e_cross_language_client/go.mod, go/go.mod, go/otel/go.mod, rust/Cargo.toml |
| dependency_bot_commit_share | 0 |
Code legibility for models
82Excellent
How it's scored
| 27/45 | Type-checkable code — Python with type-check config (src/provide/telemetry/py.typed, typescript/examples/tsconfig.json, typescript/tsconfig.json) |
| 55/55 | Manageable file sizes — 0/1,272 source files over 60KB |
Inputs used
| primary_language | Python |
| largest_source_bytes | 34,324 |
| source_files_sampled | 1,272 |
| oversized_source_files | 0 |
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
0GitHub stars
1contributors
1,241commits, last 12 months
6days since last push
20releases
1bus factor
2open issues
crates.io, Go, npm, PyPIpackage ecosystems
Data collection warnings
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
More detail
OpenSSF Scorecard 7.5 / 10
7.5aggregate
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| n/a | Branch-Protection | internal 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 |
| 10 | CI-Tests | 22 out of 22 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 |
| 0 | Code-Review | Found 0/25 approved changesets -- score normalized to 0 |
| 6 | Contributors | project has 2 contributing companies or organizations -- score normalized to 6 |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 10 | Fuzzing | project is fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 |
| 10 | Packaging | packaging workflow detected |
| 9 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 9 |
| 10 | SAST | SAST tool is run on all commits |
| 10 | Security-Policy | security policy file detected |
| 8 | Signed-Releases | 5 out of the last 5 releases have a total of 5 signed artifacts. |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 5 | Vulnerabilities | 5 existing vulnerabilities detected |
Direct dependencies 29
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| Go | github.com/google/uuid | v1.6.0 | go/go.mod |
| Go | github.com/hashicorp/golang-lru/v2 | v2.0.7 | go/go.mod |
| Go | gopkg.in/yaml.v3 | v3.0.1 | go/go.mod |
| PyPI | structlog | >=24.0.0 | pyproject.toml |
| crates.io | base64 | 0.23 | rust/Cargo.toml |
| crates.io | bcrypt | 0.19 | rust/Cargo.toml |
| crates.io | hmac | 0.13 | rust/Cargo.toml |
| crates.io | http | 1.1 | rust/Cargo.toml |
| crates.io | log | 0.4 | rust/Cargo.toml |
| crates.io | opentelemetry | 0.33 | rust/Cargo.toml |
| crates.io | opentelemetry-otlp | 0.33 | rust/Cargo.toml |
| crates.io | opentelemetry_sdk | 0.33 | rust/Cargo.toml |
| crates.io | opentelemetry-semantic-conventions | 0.33 | rust/Cargo.toml |
| crates.io | percent-encoding | 2.3.1 | rust/Cargo.toml |
| crates.io | rand | 0.10 | rust/Cargo.toml |
| crates.io | rustls | 0.23 | rust/Cargo.toml |
| crates.io | reqwest | 0.13 | rust/Cargo.toml |
| crates.io | regex | 1.11.1 | rust/Cargo.toml |
| crates.io | serde | 1.0 | rust/Cargo.toml |
| crates.io | serde_json | 1.0 | rust/Cargo.toml |
| crates.io | serde-saphyr | 1.3 | rust/Cargo.toml |
| crates.io | sha2 | 0.11 | rust/Cargo.toml |
| crates.io | thiserror | 2.0 | rust/Cargo.toml |
| crates.io | tokio | 1.44 | rust/Cargo.toml |
| crates.io | tokio-stream | 0.1 | rust/Cargo.toml |
| crates.io | url | 2 | rust/Cargo.toml |
| crates.io | uuid | 1.18 | rust/Cargo.toml |
| npm | @opentelemetry/api | ^1.9.1 | typescript/package.json |
| npm | pino | ^10.3.1 | typescript/package.json |
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
Dependency advisories 0
Installing pypi:provide-telemetry@0.11.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.34.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — PyPI, Go, crates.io, npm.