Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 05:42 UTC

team-telnyx / edge-compute

Edge Compute CLI tool

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 AI Readiness (80/100) and lowest on Community & Adoption (16/100). It was last updated 8 days ago. 2 contributors account 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
270 followers270 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?

69Good · 21% of overall
How it's scored
28.8/36Push recencylast push 8 days ago
6.9/36Commit cadence10/52 weeks with commits
11.7/18Commit volume19 commits in the last year
8/10OpenSSF Scorecard: Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year19
human_commit_share1
days_since_last_push8
active_weeks_last_year10
How it's scored
27/27Ships releases13 releases published
36/36Release recencylatest release 8 days ago
27/27Release cadencea release every ~8.5 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count13
latest_release_tagv0.5.2
releases_from_tagsno
days_since_latest_release8
mean_days_between_releases8.5

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/60Stars4 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars4
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno 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?

64Moderate · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.6/22.5Commit distributiontop contributor authored 35% of commits
8.1/13.5Contributor breadth6 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor2
contributors_sampled6
top_contributor_share0.35
How it's scored
14/42Issue resolution33% of issues closed
26.5/30PR acceptance15/17 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/16 approved changesets -- score normalized to 0
Inputs used
merged_prs15
open_issues2
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d5
prs_decided_30d5
issue_closed_ratio0.333
closed_unmerged_prs2
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
17.5/25Owner reach270 followers of team-telnyx
25/25Track record270 public repos, account ~11 yr old
Inputs used
followers270
owner_typeOrganization
is_verifiedyes
owner_loginteam-telnyx
public_repos270
account_age_days4,264

Engineering Quality

Are baseline engineering and documentation practices in place?

21At 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-Tests0 out of 15 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

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
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?

28At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests0 out of 15 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/16 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
6/7.5Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate2.8
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 instructionsAGENTS.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://developers.telnyx.com/llms.txt)
40/40Legible commit history19 of 20 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.95
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes3,698
How it's scored
18/18One-command bootstrapexamples/go/Makefile, examples/js/Makefile, examples/python/Makefile, examples/ts/Makefile
0/22Automated tests
0/11Lint / format config
11/11Static type checkingexamples/ts/call-event-router/tsconfig.json, examples/ts/mcp-server/tsconfig.json
10/10Reproducible environmentDockerfile
10/10Demonstrated agent practice2 of the last 20 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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.1
toolchain_manifestsexamples/go/middleware-patterns/go.mod
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeprimary language unknown
55/55Manageable file sizes0/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 servernot applicable to this kind of software
40/40Runnable examplesexamples
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
19commits, last 12 months
8days since last push
13releases
2bus factor
2open 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 2.8 / 10
2.8aggregate

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 05:42 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 15 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/16 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
8Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
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
PyPIpyjwtindirect
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.