Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-20 13:15 UTC

team-telnyx / edge-compute

Telnyx Edge Compute CLI: deploy serverless edge functions with KV, SQL databases and stateful actors for voice AI apps.

No license detected★ 4 stars⑂ 1 forksince Sep 2025View on GitHub ↗

team-telnyx/edge-compute holds a health index of 41 out of 100, placing it in the Weak band. It scores highest on Vitality (80/100) and lowest on Community & Adoption (16/100). It was last updated today. A single contributor accounts for most of its recent work.

41
overall / 100
Weak

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.

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

Ownership

telnyxOrganization · verified domain
309 followers291 public repossince Jan 2015

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?

80Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
13.8/36Commit cadence — 20/52 weeks with commits
13.8/18Commit volume — 33 commits in the last year
10/10OpenSSF Scorecard: Maintained — 17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year33
human_commit_share1
days_since_last_push0
active_weeks_last_year20
How it's scored
27/27Ships releases — 31 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~4.2 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count31
latest_release_tagv0.6.1
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases4.2

Community & Adoption

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

16Critical · 17% of overall
How it's scored
7.7/60Stars — 4 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars4
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

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

52Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.3/22.5Commit distribution — top contributor authored 63% of commits
8.1/13.5Contributor breadth — 6 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.629
How it's scored
10.5/42Issue resolution — 25% of issues closed
28.1/30PR acceptance — 30/32 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/28 approved changesets -- score normalized to 0
Inputs used
merged_prs30
open_issues3
closed_issues1
prs_merged_7d1
prs_decided_7d1
prs_merged_30d6
prs_decided_30d6
issue_closed_ratio0.25
closed_unmerged_prs2
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
17.9/25Owner reach — 309 followers of team-telnyx
25/25Track record — 291 public repos, account ~11 yr old
Inputs used
followers309
owner_typeOrganization
is_verifiedyes
owner_loginteam-telnyx
public_repos291
account_age_days4,328

Engineering Quality

Are baseline engineering and documentation practices in place?

25At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 28 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 20 topics
10/10Wiki
Inputs used
topicsai-call-assistant, ai-phone-agent, ai-receptionist, ai-voice-agent, ai-voice-agents, aws-lambda-alternative, cloudflare-workers-alternative, edge-compute, edge-database, edge-functions, edge-inference, inference-gateway, platform-as-a-service, serverless-agents, serverless-computing, serverless-database, serverless-sql, stateful-actors, twilio-functions, voice-ai-agent
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

30At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — 0 out of 28 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
0/7.5Code-Review — Found 0/28 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
7.5/7.5Maintained — 17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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 — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Token-Permissions. 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.

80Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://developers.telnyx.com/llms.txt)
40/40Legible commit history — 34 of 35 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://developers.telnyx.com/llms.txt
legible_history_share0.971
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes3,698
How it's scored
18/18One-command bootstrap — examples/go/Makefile, examples/js/Makefile, examples/python/Makefile, examples/ts/Makefile
0/22Automated tests
0/11Lint / format config
11/11Static type checking — examples/ts/call-event-router/tsconfig.json, examples/ts/mcp-server/tsconfig.json
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 2 of the last 35 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_testsno
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_filesexamples/go/Makefile, examples/js/Makefile, examples/python/Makefile, examples/ts/Makefile
has_devcontainerno
has_linter_configno
typecheck_configsexamples/ts/call-event-router/tsconfig.json, examples/ts/mcp-server/tsconfig.json
agent_commit_share0.057
toolchain_manifestsexamples/go/middleware-patterns/go.mod
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — primary language unknown
55/55Manageable file sizes — 0/22 source files over 60KB
Inputs used
primary_language—
largest_source_bytes29,967
source_files_sampled22
oversized_source_files0
Excluded from scoring (no data or not applicable): Type-checkable code. Remaining weights renormalized.
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
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

4GitHub stars
6contributors
33commits, last 12 months
0days since last push
31releases
1bus factor
3open issues
—package ecosystems

Data collection warnings

  • Language breakdown unavailable
  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 3.0 / 10
3.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-11-20 13:15 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 28 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/28 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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.
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 23

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

RegistryPackageVersionRelation
npm@modelcontextprotocol/sdk^1.12.1indirect
npm@types/express^4.17.21indirect
npm@types/node^18.0.0indirect
npm@types/node^20.0.0indirect
npm@types/qs^6.9.17indirect
npm@types/yargs^17.0.33indirect
npm@valtown/deno-http-worker^2.0.1indirect
npmdeno^2.7.13indirect
npmexpress^4.21.0indirect
npmfuse.js^7.3.0indirect
npmminisearch^7.2.0indirect
npmpino^9.6.0indirect
npmpino-http^10.4.0indirect
npmpino-pretty^13.0.0indirect
npmqs^6.13.0indirect
npmtelnyx^6.41.0indirect
npmtelnyx-mcp^6.41.1indirect
npmts-node^10.9.0indirect
npmtypescript^5.0.0indirect
npmws^8.20.0indirect
npmyargs^17.7.2indirect
npmzod^3.24.0indirect
PyPIpyjwt—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.