Public recordGood
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 07:12 UTC
imqueue / opentelemetry
OpenTelemetry instrumentation for @imqueue — every RPC traced, with no changes to service or client code
imqueue/opentelemetry holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (71/100) and lowest on Community & Adoption (42/100). It was last updated 40 days ago. A single contributor accounts for most of its recent work.
67
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.
67
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 61 is calibrated to 67 on the published index scale (record calibration 2026-08-02).
Ownership
@imqueueOrganization
8 followers31 public repossince Apr 2018
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 |
|---|---|---|---|---|---|---|
| npm | @imqueue/opentelemetry | 4.1.3 | 2,741 | 5 | 40 days ago | imqueueimqtracetracingopentelemetryotelapmobservabilityrpcintegrationinstrumentation |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
69
Development activity
48Weak
How it's scored
| 18/36 | Push recency — last push 40 days ago |
| 6.2/36 | Commit cadence — 9/52 weeks with commits |
| 13.3/18 | Commit volume — 29 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 29 |
| human_commit_share | 0.984 |
| days_since_last_push | 40 |
| active_weeks_last_year | 9 |
Release discipline
100Exceptional
How it's scored
| 27/27 | Ships releases — 8 releases published |
| 36/36 | Release recency — latest release 40 days ago |
| 27/27 | Release cadence — a release every ~6 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 8 |
| latest_release_tag | v4.1.3 |
| releases_from_tags | no |
| days_since_latest_release | 40 |
| mean_days_between_releases | 6 |
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?
42
Popularity & adoption
1Critical
How it's scored
| 0/60 | Stars — 0 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 1 watchers |
Inputs used
| forks | 0 |
| stars | 0 |
| watchers | 1 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
77Good
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (GPL-3.0) |
| 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 | yes |
| readme_badges | 0 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | yes |
Ecosystem adoption (downloads)
57Moderate
How it's scored
| 45.8/80 | Monthly downloads — 2,741 downloads/month across npm |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | @imqueue/opentelemetry |
| dependents | — |
| ecosystems | npm |
| total_downloads | — |
| monthly_downloads | 2,741 |
| 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?
60
Maintainer resilience (bus factor)
29At Risk
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 10.2/22.5 | Commit distribution — top contributor authored 55% of commits |
| 4.1/13.5 | Contributor breadth — 3 contributors |
| 6/10 | OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 3 |
| top_contributor_share | 0.545 |
How it's scored
| 0/42 | Issue resolution — no issues or no data |
| 30/30 | PR acceptance — 5/5 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/30 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 5 |
| open_issues | 0 |
| closed_issues | 0 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | — |
| closed_unmerged_prs | 0 |
| 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): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
60Moderate
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain |
| 6.9/25 | Owner reach — 8 followers of imqueue |
| 23/25 | Track record — 31 public repos, account ~8 yr old |
Inputs used
| followers | 8 |
| owner_type | Organization |
| is_verified | no |
| owner_login | imqueue |
| public_repos | 31 |
| account_age_days | 3,102 |
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on npm |
| 35/35 | Publish recency — latest publish 40 days ago |
| 20/20 | Version history — 5 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | @imqueue/opentelemetry |
| ecosystems | npm |
| any_deprecated | no |
| min_days_since_publish | 40 |
Engineering Quality
Are baseline engineering and documentation practices in place?
71
Engineering practices
68Good
How it's scored
| 24/24 | CI workflows — 5 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 — 1 out of 1 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
75Good
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://imqueue.org |
| 10/10 | Repository description |
| 10/10 | Topics — 9 topics |
| 10/10 | Wiki |
Inputs used
| topics | imqueue, instrumentation, nodejs, observability, opentelemetry, tracing, apm, otel, typescript |
| has_wiki | yes |
| homepage | https://imqueue.org |
| docs_site | https://imqueue.org |
| 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?
64
Security posture
55Moderate
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 2.2/7.5 | Branch-Protection — branch protection is not maximal on development and all release branches |
| 2.5/2.5 | CI-Tests — 1 out of 1 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/30 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 |
| 0/7.5 | Dependency-Update-Tool — no update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 1.5/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3 |
| 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 |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 6/7.5 | Vulnerabilities — 2 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 16 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 2 |
| scorecard_aggregate | 5.5 |
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 | 10 |
| 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 npm:@imqueue/opentelemetry@4.1.3 runtime dependency closure — what installing the published package pulls in — 10 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.
56
Agent context & guidance
44Weak
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 15/15 | Machine-readable docs (llms.txt) — llms.txt served by the project website (https://imqueue.org/llms.txt) |
| 29.3/40 | Legible commit history — 33 of 60 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | yes |
| llms_txt_url | https://imqueue.org/llms.txt |
| legible_history_share | 0.55 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 11/11 | Static type checking — tsconfig.json |
| 10/10 | Reproducible environment — lockfile |
| 3.3/10 | Demonstrated agent practice — 1 of the last 61 commits agent-authored or agent-credited |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 3/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | package-lock.json |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | tsconfig.json |
| agent_commit_share | 0.016 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
Code legibility for models
100Exceptional
How it's scored
| 45/45 | Type-checkable code — TypeScript (statically typed) |
| 55/55 | Manageable file sizes — 0/12 source files over 60KB |
Inputs used
| primary_language | TypeScript |
| largest_source_bytes | 16,993 |
| source_files_sampled | 12 |
| oversized_source_files | 0 |
Key facts
0GitHub stars
3contributors
29commits, last 12 months
40days since last push
8releases
1bus factor
0open issues
npmpackage ecosystems
More detail
OpenSSF Scorecard 5.5 / 10
5.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 |
| 3 | Branch-Protection | branch protection is not maximal on development and all release branches |
| 10 | CI-Tests | 1 out of 1 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/30 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 |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| 3 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 3 |
| 10 | SAST | SAST tool is run on all commits |
| 10 | Security-Policy | security policy file detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 8 | Vulnerabilities | 2 existing vulnerabilities detected |
Direct dependencies 2
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | @opentelemetry/api | ^1.9.1 | package.json |
| npm | @opentelemetry/instrumentation | ^0.220.0 | package.json |
All dependencies 75
Full resolved dependency set from the GitHub dependency graph: 2 direct and 73 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| npm | @opentelemetry/api | 1.9.1 | direct |
| npm | @opentelemetry/instrumentation | 0.220.0 | direct |
| npm | @opentelemetry/api-logs | 0.220.0 | indirect |
| npm | @opentelemetry/context-async-hooks | 2.9.0 | indirect |
| npm | @oxfmt/binding-android-arm-eabi | 0.57.0 | indirect |
| npm | @oxfmt/binding-android-arm64 | 0.57.0 | indirect |
| npm | @oxfmt/binding-darwin-arm64 | 0.57.0 | indirect |
| npm | @oxfmt/binding-darwin-x64 | 0.57.0 | indirect |
| npm | @oxfmt/binding-freebsd-x64 | 0.57.0 | indirect |
| npm | @oxfmt/binding-linux-arm-gnueabihf | 0.57.0 | indirect |
| npm | @oxfmt/binding-linux-arm-musleabihf | 0.57.0 | indirect |
| npm | @oxfmt/binding-linux-arm64-gnu | 0.57.0 | indirect |
| npm | @oxfmt/binding-linux-arm64-musl | 0.57.0 | indirect |
| npm | @oxfmt/binding-linux-ppc64-gnu | 0.57.0 | indirect |
| npm | @oxfmt/binding-linux-riscv64-gnu | 0.57.0 | indirect |
| npm | @oxfmt/binding-linux-riscv64-musl | 0.57.0 | indirect |
| npm | @oxfmt/binding-linux-s390x-gnu | 0.57.0 | indirect |
| npm | @oxfmt/binding-linux-x64-gnu | 0.57.0 | indirect |
| npm | @oxfmt/binding-linux-x64-musl | 0.57.0 | indirect |
| npm | @oxfmt/binding-openharmony-arm64 | 0.57.0 | indirect |
| npm | @oxfmt/binding-win32-arm64-msvc | 0.57.0 | indirect |
| npm | @oxfmt/binding-win32-ia32-msvc | 0.57.0 | indirect |
| npm | @oxfmt/binding-win32-x64-msvc | 0.57.0 | indirect |
| npm | @oxlint/binding-android-arm-eabi | 1.72.0 | indirect |
| npm | @oxlint/binding-android-arm64 | 1.72.0 | indirect |
| npm | @oxlint/binding-darwin-arm64 | 1.72.0 | indirect |
| npm | @oxlint/binding-darwin-x64 | 1.72.0 | indirect |
| npm | @oxlint/binding-freebsd-x64 | 1.72.0 | indirect |
| npm | @oxlint/binding-linux-arm-gnueabihf | 1.72.0 | indirect |
| npm | @oxlint/binding-linux-arm-musleabihf | 1.72.0 | indirect |
| npm | @oxlint/binding-linux-arm64-gnu | 1.72.0 | indirect |
| npm | @oxlint/binding-linux-arm64-musl | 1.72.0 | indirect |
| npm | @oxlint/binding-linux-ppc64-gnu | 1.72.0 | indirect |
| npm | @oxlint/binding-linux-riscv64-gnu | 1.72.0 | indirect |
| npm | @oxlint/binding-linux-riscv64-musl | 1.72.0 | indirect |
| npm | @oxlint/binding-linux-s390x-gnu | 1.72.0 | indirect |
| npm | @oxlint/binding-linux-x64-gnu | 1.72.0 | indirect |
| npm | @oxlint/binding-linux-x64-musl | 1.72.0 | indirect |
| npm | @oxlint/binding-openharmony-arm64 | 1.72.0 | indirect |
| npm | @oxlint/binding-win32-arm64-msvc | 1.72.0 | indirect |
| npm | @oxlint/binding-win32-ia32-msvc | 1.72.0 | indirect |
| npm | @oxlint/binding-win32-x64-msvc | 1.72.0 | indirect |
| npm | @types/node | 24.13.3 | indirect |
| npm | @typescript/typescript-aix-ppc64 | 7.0.2 | indirect |
| npm | @typescript/typescript-darwin-arm64 | 7.0.2 | indirect |
| npm | @typescript/typescript-darwin-x64 | 7.0.2 | indirect |
| npm | @typescript/typescript-freebsd-arm64 | 7.0.2 | indirect |
| npm | @typescript/typescript-freebsd-x64 | 7.0.2 | indirect |
| npm | @typescript/typescript-linux-arm | 7.0.2 | indirect |
| npm | @typescript/typescript-linux-arm64 | 7.0.2 | indirect |
| npm | @typescript/typescript-linux-loong64 | 7.0.2 | indirect |
| npm | @typescript/typescript-linux-mips64el | 7.0.2 | indirect |
| npm | @typescript/typescript-linux-ppc64 | 7.0.2 | indirect |
| npm | @typescript/typescript-linux-riscv64 | 7.0.2 | indirect |
| npm | @typescript/typescript-linux-s390x | 7.0.2 | indirect |
| npm | @typescript/typescript-linux-x64 | 7.0.2 | indirect |
| npm | @typescript/typescript-netbsd-arm64 | 7.0.2 | indirect |
| npm | @typescript/typescript-netbsd-x64 | 7.0.2 | indirect |
| npm | @typescript/typescript-openbsd-arm64 | 7.0.2 | indirect |
| npm | @typescript/typescript-openbsd-x64 | 7.0.2 | indirect |
| npm | @typescript/typescript-sunos-x64 | 7.0.2 | indirect |
| npm | @typescript/typescript-win32-arm64 | 7.0.2 | indirect |
| npm | @typescript/typescript-win32-x64 | 7.0.2 | indirect |
| npm | cjs-module-lexer | 2.2.0 | indirect |
| npm | debug | 4.4.3 | indirect |
| npm | es-module-lexer | 2.3.0 | indirect |
| npm | import-in-the-middle | 3.3.1 | indirect |
| npm | module-details-from-path | 1.0.4 | indirect |
| npm | ms | 2.1.3 | indirect |
| npm | oxfmt | 0.57.0 | indirect |
| npm | oxlint | 1.72.0 | indirect |
| npm | require-in-the-middle | 8.0.1 | indirect |
| npm | tinypool | 2.1.0 | indirect |
| npm | typescript | 7.0.2 | indirect |
| npm | undici-types | 7.18.2 | indirect |
Dependency advisories 0
Installing npm:@imqueue/opentelemetry@4.1.3 pulls in 10 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 — npm.