Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 00:31 UTC

drachtio / drachtio-server

A SIP call processing server that can be controlled via nodejs applications

C++MIT★ 331 stars⑂ 123 forkssince Dec 2013View on GitHub ↗

drachtio/drachtio-server holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Engineering Quality (76/100) and lowest on Security (52/100). It was last updated 27 days ago. A single contributor accounts for most of its recent work.

65
overall / 100
Good

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.

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

Ownership

drachtio.orgOrganization · verified domain
78 followers40 public repossince Jul 2019

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

Metrics by category

Vitality

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

53Moderate · 21% of overall
How it's scored
28.8/36Push recency — last push 27 days ago
11.1/36Commit cadence — 16/52 weeks with commits
13.5/18Commit volume — 31 commits in the last year
6/10OpenSSF Scorecard: Maintained — 7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year31
human_commit_share1
days_since_last_push27
active_weeks_last_year16
How it's scored
27/27Ships releases — 3 releases published
0/36Release recency — latest release 3,154 days ago
12.6/27Release cadence — a release every ~195 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv0.7.2-rc1
releases_from_tagsno
days_since_latest_release3,154
mean_days_between_releases195
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?

59Moderate · 17% of overall
How it's scored
40.9/60Stars — 331 stars
17.4/25Forks — 123 forks
7.7/15Watchers — 25 watchers
Inputs used
forks123
stars331
watchers25
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno

Sustainability & Governance

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

58Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.7/22.5Commit distribution — top contributor authored 92% of commits
13.5/13.5Contributor breadth — 17 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled17
top_contributor_share0.924
How it's scored
23.4/42Issue resolution — 56% of issues closed
24.9/30PR acceptance — 145/175 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 12/30 approved changesets -- score normalized to 4
Inputs used
merged_prs145
open_issues128
closed_issues160
prs_merged_7d0
prs_decided_7d3
prs_merged_30d1
prs_decided_30d4
issue_closed_ratio0.556
closed_unmerged_prs30
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.6/25Owner reach — 78 followers of drachtio
23.7/25Track record — 40 public repos, account ~7 yr old
Inputs used
followers78
owner_typeOrganization
is_verifiedyes
owner_logindrachtio
public_repos40
account_age_days2,619

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 16 out of 25 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://drachtio.org
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicssip, drachtio, drachtio-srf, nodejs
has_wikiyes
homepagehttps://drachtio.org
docs_sitehttps://drachtio.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
1.5/2.5CI-Tests — 16 out of 25 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
3/7.5Code-Review — Found 12/30 approved changesets -- score normalized to 4
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
4.5/7.5Maintained — 7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0.5/5SAST — SAST tool is not run on all commits -- score normalized to 1
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 20 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories22
affected_packages10
assessed_packages143
unassessed_packages8
affected_by_severitycritical 1, high 5, moderate 3, unknown 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 143 resolved dependencies against OSV. 8 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

62Moderate · 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 — 76 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.76
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — test/leak-repro/go.mod (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — C++ (statically typed)
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 10 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, package-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.1
toolchain_manifeststest/leak-repro/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C++ (statically typed)
52.7/55Manageable file sizes — 3/71 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes150,912
source_files_sampled71
oversized_source_files3

Key facts

331GitHub stars
17contributors
31commits, last 12 months
27days since last push
3releases
1bus factor
128open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 123 ⇿
0Stars
123Forks
3Releases

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.

025507510012512142015-072021-022026-08
Major 0Minor 1Patch 1

Each point covers 11 days.

OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-09-17 00:30 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal 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
6CI-Tests16 out of 25 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 12/30 approved changesets -- score normalized to 4
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
1SASTSAST tool is not run on all commits -- score normalized to 1
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities20 existing vulnerabilities detected
All dependencies 151

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

RegistryPackageVersionRelation
Gogithub.com/emiago/sipgov1.3.1indirect
Gogithub.com/gobwas/httpheadv0.1.0indirect
Gogithub.com/gobwas/poolv0.2.1indirect
Gogithub.com/gobwas/wsv1.3.2indirect
Gogithub.com/google/uuidv1.6.0indirect
Gogithub.com/icholy/digestv1.1.0indirect
Gogolang.org/x/syncv0.16.0indirect
Gogolang.org/x/sysv0.24.0indirect
npm@eslint/eslintrc1.4.1indirect
npm@humanwhocodes/config-array0.11.8indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/object-schema1.2.1indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npmabort-controller3.0.0indirect
npmacorn8.8.1indirect
npmacorn-jsx5.3.2indirect
npmajv6.12.6indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmany-base1.1.0indirect
npmargparse2.0.1indirect
npmasync^2.6.0indirect
npmatomic-sleep1.0.0indirect
npmbalanced-match1.0.2indirect
npmbase64-js1.5.1indirect
npmblue-tape^1.0.0indirect
npmbody-parser^1.18.3indirect
npmbrace-expansion1.1.11indirect
npmbuffer6.0.3indirect
npmcallsites3.1.0indirect
npmchalk4.1.2indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.3indirect
npmdebug3.2.7indirect
npmdebug4.3.4indirect
npmdebug^3.1.0indirect
npmdeep-is0.1.4indirect
npmdelegates0.1.0indirect
npmdoctrine3.0.0indirect
npmdrachtio-mw-registration-parser0.1.0indirect
npmdrachtio-srf4.5.22indirect
npmdrachtio-srf^5.0.1indirect
npmescape-string-regexp4.0.0indirect
npmeslint8.32.0indirect
npmeslint-plugin-promise6.1.1indirect
npmeslint-scope7.1.1indirect
npmeslint-utils3.0.0indirect
npmeslint-visitor-keys2.1.0indirect
npmeslint-visitor-keys3.3.0indirect
npmespree9.4.1indirect
npmesquery1.4.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmevent-target-shim5.0.1indirect
npmevents3.3.0indirect
npmexpress4.16.3indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfast-redact3.1.2indirect
npmfastq1.15.0indirect
npmfile-entry-cache6.0.1indirect
npmfind-up5.0.0indirect
npmflat-cache3.0.4indirect
npmflatted3.2.7indirect
npmfs.realpath1.0.0indirect
npmglob7.2.3indirect
npmglob-parent6.0.2indirect
npmglobals13.19.0indirect
npmgrapheme-splitter1.0.4indirect
npmhas-flag4.0.0indirect
npmieee7541.2.1indirect
npmignore5.2.4indirect
npmimport-fresh3.3.0indirect
npmimurmurhash0.1.4indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-path-inside3.0.3indirect
npmisexe2.0.0indirect
npmjs-sdsl4.3.0indirect
npmjs-yaml4.1.0indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmlodash.merge4.6.2indirect
npmminimatch3.1.2indirect
npmminimist^1.2.0indirect
npmms2.1.2indirect
npmms2.1.3indirect
npmnatural-compare1.4.0indirect
npmnode-noop0.0.1indirect
npmon-exit-leak-free2.1.0indirect
npmonce1.4.0indirect
npmonly0.0.2indirect
npmoptionator0.9.1indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmparent-module1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-key3.1.1indirect
npmpino8.8.0indirect
npmpino^6.6.1indirect
npmpino-abstract-transport1.0.0indirect
npmpino-std-serializers6.1.0indirect
npmprelude-ls1.2.1indirect
npmprocess0.11.10indirect
npmprocess-warning2.1.0indirect
npmpunycode2.3.0indirect
npmqueue-microtask1.2.3indirect
npmquick-format-unescaped4.0.4indirect
npmreadable-stream4.3.0indirect
npmreal-require0.2.0indirect
npmregexpp3.2.0indirect
npmresolve-from4.0.0indirect
npmreusify1.0.4indirect
npmrimraf3.0.2indirect
npmrun-parallel1.2.0indirect
npmsafe-stable-stringify2.4.2indirect
npmsdp-transform2.14.1indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmshort-uuid4.2.2indirect
npmsip-methods0.3.0indirect
npmsip-status0.1.0indirect
npmsonic-boom3.2.1indirect
npmsplit24.1.0indirect
npmstrip-ansi6.0.1indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmtape^4.14.0indirect
npmtext-table0.2.0indirect
npmthread-stream2.3.0indirect
npmtype-check0.4.0indirect
npmtype-fest0.20.2indirect
npmuri-js4.4.1indirect
npmutils-merge1.0.1indirect
npmuuid8.3.2indirect
npmuuid-random1.3.2indirect
npmwhich2.0.2indirect
npmword-wrap1.2.3indirect
npmwrappy1.0.2indirect
npmyocto-queue0.1.0indirect
Dependency advisories 10

This repository publishes no package the index resolves, so its own dependency graph was assessed — 143 packages, which also include development and test pins that never ship: 10 carry known advisories, of which 0 are direct. 8 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
flatted3.2.7indirectcritical23.4.2
brace-expansion1.1.11indirecthigh55.0.9
cross-spawn7.0.3indirecthigh17.0.5
js-yaml4.1.0indirecthigh54.3.2
minimatch3.1.2indirecthigh310.2.3
uuid8.3.2indirecthigh113.0.1
ajv6.12.6indirectmoderate18.18.0
express4.16.3indirectmoderate25.0.0-beta.3
word-wrap1.2.3indirectmoderate11.2.4
golang.org/x/sysv0.24.0indirectunknown10.44.0

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.

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.