Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-06 07:54 UTC

nshkrdotcom / execution_plane

Execution Plane is an Elixir/OTP runtime substrate for boundary-aware AI infrastructure, unifying process execution, protocol framing, transport lifecycle, realtime streams, JSON-RPC control lanes, and future sandbox-backed placement under one composable kernel for agentic systems.

ElixirMIT★ 2 stars⑂ 0 forkssince Apr 2026View on GitHub ↗

nshkrdotcom/execution_plane holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on Vitality (76/100) and lowest on Security (30/100). It was last updated 18 days ago. A single contributor accounts for most of its recent work.

45
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.

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

Ownership

nshkrdotcomPersonal account
75 followers356 public repossince Mar 2023

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Hexexecution_plane0.3.02,031656 days ago
Hexexecution_plane_http0.2.0330218 days ago
Hexexecution_plane_process0.3.11,617618 days ago
Hexexecution_plane_jsonrpc0.2.01,507256 days ago

Metrics by category

Vitality

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

76Good · 21% of overall
How it's scored
28.8/36Push recency — last push 18 days ago
11.1/36Commit cadence — 16/52 weeks with commits
18/18Commit volume — 124 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year124
human_commit_share1
days_since_last_push18
active_weeks_last_year16
How it's scored
16.2/27Ships releases — 7 version tags (no GitHub releases)
36/36Release recency — latest release 18 days ago
27/27Release cadence — a release every ~10.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tagv0.3.1
releases_from_tagsyes
days_since_latest_release18
mean_days_between_releases10.9
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?

33At Risk · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars2
watchers0
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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
49.9/80Monthly downloads — 5,485 downloads/month across hex
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesexecution_plane, execution_plane_http, execution_plane_process, execution_plane_jsonrpc
dependents—
ecosystemshex
total_downloads16,452
monthly_downloads5,485
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?

37Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
13.5/25Owner reach — 75 followers of nshkrdotcom
20.2/25Track record — 356 public repos, account ~3 yr old
Inputs used
followers75
owner_typeUser
is_verified—
owner_loginnshkrdotcom
public_repos356
account_age_days1,310
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 4 package(s) on hex
35/35Publish recency — latest publish 18 days ago
20/20Version history — 6 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesexecution_plane, execution_plane_http, execution_plane_process, execution_plane_jsonrpc
ecosystemshex
any_deprecatedno
min_days_since_publish18

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 20 topics
10/10Wiki
Inputs used
topicsagent-infrastructure, ai-infrastructure, developer-platform, distributed-systems, elixir, execution-engine, json-rpc, nshkr-ai-infra, boundary-systems, execution-plane, application-runtime, execution-runtime, integration-runtime, job-orchestration, message-framing, boundary-runtime, kernel-runtime, machine-infrastructure, microvm-ready, modular-runtime
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
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
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 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
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
3/7.5Vulnerabilities — 6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, 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.

61Moderate · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
20.3/40Legible commit history — 38 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.38
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes15,016
How it's scored
12.6/18One-command bootstrap — core/execution_plane/mix.exs, mix.exs, packaging/weld/execution_plane/consumer/mix.exs (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — 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 — no data
Inputs used
has_nixno
has_testsyes
lockfilesmix.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.1
toolchain_manifestscore/execution_plane/mix.exs, mix.exs, packaging/weld/execution_plane/consumer/mix.exs, protocols/execution_plane_http/mix.exs, protocols/execution_plane_jsonrpc/mix.exs, runtimes/execution_plane_node/mix.exs, runtimes/execution_plane_operator_terminal/mix.exs, runtimes/execution_plane_process/mix.exs, streaming/execution_plane_sse/mix.exs, streaming/execution_plane_websocket/mix.exs
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — Elixir without a type-check config
55/55Manageable file sizes — 0/223 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes40,765
source_files_sampled223
oversized_source_files0

Key facts

2GitHub stars
1contributors
124commits, last 12 months
18days since last push
7releases
1bus factor
0open issues
Hexpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch hex package 'execution_plane_workspace' from its registry
  • Could not fetch hex package 'execution_plane_node' from its registry
  • Could not fetch hex package 'execution_plane_sse' from its registry
  • Could not fetch hex package 'execution_plane_websocket' from its registry
  • Could not fetch hex package 'execution_plane_operator_terminal' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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-10-06 07:54 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 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
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 35
RegistryPackageVersion constraintManifest
Hexblitz~> 0.3.0mix.exs
Hexground_plane_contracts~> 0.1.0core/execution_plane/mix.exs
Hexground_plane_persistence_policy~> 0.1.0core/execution_plane/mix.exs
Hexjason~> 1.4.5core/execution_plane/mix.exs
Hextelemetry~> 1.4.2core/execution_plane/mix.exs
Hexjason~> 1.4.5protocols/execution_plane_http/mix.exs
Hexexecution_plane—protocols/execution_plane_http/mix.exs
Hexjason~> 1.4.5protocols/execution_plane_jsonrpc/mix.exs
Hexexecution_plane—protocols/execution_plane_jsonrpc/mix.exs
Hexexecution_plane—protocols/execution_plane_jsonrpc/mix.exs
Hexexecution_plane—protocols/execution_plane_jsonrpc/mix.exs
Hexjason~> 1.4.5runtimes/execution_plane_node/mix.exs
Hextelemetry~> 1.4.2runtimes/execution_plane_node/mix.exs
Hexexecution_plane—runtimes/execution_plane_node/mix.exs
Hexexecution_plane—runtimes/execution_plane_node/mix.exs
Hexexecution_plane—runtimes/execution_plane_node/mix.exs
Hexex_ratatui~> 0.11.1runtimes/execution_plane_operator_terminal/mix.exs
Hexexecution_plane~> 0.3.0runtimes/execution_plane_process/mix.exs
Hexground_plane_contracts~> 0.1.1runtimes/execution_plane_process/mix.exs
Hexerlexec~> 2.4runtimes/execution_plane_process/mix.exs
Hexjason~> 1.4.5runtimes/execution_plane_process/mix.exs
Hextelemetry~> 1.4.2runtimes/execution_plane_process/mix.exs
Hexfinch~> 0.23.0streaming/execution_plane_sse/mix.exs
Hexserver_sent_events~> 1.1.0streaming/execution_plane_sse/mix.exs
Hexjason~> 1.4.5streaming/execution_plane_sse/mix.exs
Hextelemetry~> 1.4.2streaming/execution_plane_sse/mix.exs
Hexexecution_plane—streaming/execution_plane_sse/mix.exs
Hexexecution_plane—streaming/execution_plane_sse/mix.exs
Hexexecution_plane—streaming/execution_plane_sse/mix.exs
Hexmint~> 1.9.3streaming/execution_plane_websocket/mix.exs
Hexmint_web_socket~> 1.0.5streaming/execution_plane_websocket/mix.exs
Hexjason~> 1.4.5streaming/execution_plane_websocket/mix.exs
Hexexecution_plane—streaming/execution_plane_websocket/mix.exs
Hexexecution_plane—streaming/execution_plane_websocket/mix.exs
Hexexecution_plane—streaming/execution_plane_websocket/mix.exs
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

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 — Hex.