Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 08:51 UTC

aryaminus / controlkeel

Agent control plane for governed AI coding: validate changes, enforce policy gates, track findings, proofs, and evals based on your habits.

ElixirCustom license★ 11 stars⑂ 1 forksince Mar 2026View on GitHub ↗
KindNetwork servicehow this is determined

aryaminus/controlkeel holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Vitality (88/100) and lowest on Community & Adoption (29/100). It was last updated today. A single contributor accounts for most of its recent work.

62
overall / 100
Moderate

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.

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

Ownership

sunimPersonal account
163 followers129 public repossince Dec 2015

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

Metrics by category

Vitality

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

88Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
17.3/36Commit cadence — 25/52 weeks with commits
18/18Commit volume — 1,377 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 29 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,377
human_commit_share0.82
days_since_last_push0
active_weeks_last_year25

Release discipline

98Exceptional
How it's scored
27/27Ships releases — 22 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~2 days
8/10OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count22
latest_release_tagv0.4.9
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases2

Community & Adoption

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

29At Risk · 17% of overall
How it's scored
16.2/60Stars — 11 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars11
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

48Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.4/22.5Commit distribution — top contributor authored 72% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.716
How it's scored
28.8/42Issue resolution — 69% of issues closed
18/30PR acceptance — 69/115 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/11 approved changesets -- score normalized to 1
Inputs used
merged_prs69
open_issues11
closed_issues24
prs_merged_7d2
prs_decided_7d2
prs_merged_30d28
prs_decided_30d60
issue_closed_ratio0.686
closed_unmerged_prs46
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
15.9/25Owner reach — 163 followers of aryaminus
25/25Track record — 129 public repos, account ~10 yr old
Inputs used
followers163
owner_typeUser
is_verified—
owner_loginaryaminus
public_repos129
account_age_days3,917
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

81Excellent · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 5 out of 5 merged PRs checked by a CI test -- score normalized to 10
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://controlkeel.com
10/10Repository description
10/10Topics — 19 topics
10/10Wiki
Inputs used
topicsagents, ai-governance, code-review, compliance, devsecops, elixir, llm, mcp, model-context-protocol, phoenix, policy-as-code, security, skills, tooling, benchmark, observability, ai-agents, compliance-as-code, evals
has_wikiyes
homepagehttps://controlkeel.com
docs_sitehttps://controlkeel.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

32At 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
2.5/2.5CI-Tests — 5 out of 5 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 2/11 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 6 contributing companies or organizations
0/10Dangerous-Workflow — dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 29 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
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
6/7.5Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 43 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate3.2

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.

66Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
25.4/40Legible commit history — 39 of 82 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.476
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes9,828
How it's scored
12.6/18One-command bootstrap — mix.exs (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — assets/tsconfig.json, packages/npm/controlkeel-sdk/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 6 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
lockfilesmix.lock, package-lock.json
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configsassets/tsconfig.json, packages/npm/controlkeel-sdk/tsconfig.json
agent_commit_share0.06
toolchain_manifestsmix.exs
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Elixir with type-check config (assets/tsconfig.json, packages/npm/controlkeel-sdk/tsconfig.json)
54.2/55Manageable file sizes — 12/814 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes243,845
source_files_sampled814
oversized_source_files12
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — priv/static/openapi.json
0/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filespriv/static/openapi.json
interfaces_expected_ofnetwork-service

Key facts

11GitHub stars
2contributors
1,377commits, last 12 months
0days since last push
22releases
1bus factor
11open issues
Hexpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 3.2 / 10
3.2aggregate

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-09 08:51 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests5 out of 5 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/11 approved changesets -- score normalized to 1
10Contributorsproject has 6 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 29 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow 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
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities43 existing vulnerabilities detected
Direct dependencies 23
RegistryPackageVersion constraintManifest
Hexphoenix~> 1.8.5mix.exs
Hexphoenix_ecto~> 4.5mix.exs
Hexecto_sql~> 3.13mix.exs
Hexecto_sqlite3>= 0.0.0mix.exs
Hexpostgrex>= 0.0.0mix.exs
Hexphoenix_html~> 4.1mix.exs
Hexphoenix_live_view~> 1.1.0mix.exs
Hexphoenix_live_dashboard~> 0.8.3mix.exs
Hexesbuild~> 0.10mix.exs
Hextailwind~> 0.3mix.exs
Hexheroiconstailwindlabs/heroiconsmix.exs
Hexreq~> 0.5mix.exs
Hexassent~> 0.3mix.exs
Hexchromic_pdf~> 1.17mix.exs
Hextelemetry_metrics~> 1.0mix.exs
Hextelemetry_poller~> 1.0mix.exs
Hexgettext~> 1.0mix.exs
Hexjason~> 1.2mix.exs
Hexyaml_elixir~> 2.11mix.exs
Hexdns_cluster~> 0.2.0mix.exs
Hexbandit~> 1.5mix.exs
Hexwebsockex~> 0.5.1mix.exs
Hexburrito~> 1.5.0mix.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.