Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 12:47 UTC

enumind / modonome

THE MODONOME Project - Governed engineering autonomy

JavaScript · TypeScriptCustom license★ 1 star⑂ 0 forkssince Jun 2026View on GitHub ↗
KindCommand-line toolWeb interfacehow this is determined

enumind/modonome holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (84/100) and lowest on Sustainability & Governance (33/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

EnuMindOrganization
0 followers3 public repossince Jun 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmmodonomepoints to another repo — not scored0.1.0-alpha1846775 days agoautonomousagentcigovernancecode-reviewmodernizationtech-debtai-safetyagenticautonomyratchetagentproof

Metrics by category

Vitality

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

64Moderate · 21% of overall
How it's scored
36/36Push recency — last push 6 days ago
3.5/36Commit cadence — 5/52 weeks with commits
18/18Commit volume — 141 commits in the last year
0/10OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year141
human_commit_share0.96
days_since_last_push6
active_weeks_last_year5
How it's scored
16.2/27Ships releases — 1 version tags (no GitHub releases)
36/36Release recency — latest release 75 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv0.1.0-alpha
releases_from_tagsyes
days_since_latest_release75
mean_days_between_releases—
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?

41Weak · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesapi.securityscorecards.dev, github.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

33At Risk · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.9/22.5Commit distribution — top contributor authored 82% of commits
2.7/13.5Contributor breadth — 2 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.825
How it's scored
0/42Issue resolution — no issues or no data
22.6/30PR acceptance — 109/145 decided PRs merged
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_prs109
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs36
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of enumind
4.8/25Track record — 3 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginenumind
public_repos3
account_age_days73

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://www.modonome.com/
10/10Repository description
10/10Topics — 10 topics
0/10Wiki
Inputs used
topicsagentic-ai, automation, secure-coding, autonomous-engineering, ci-cd, developer-tools, devops, governance, modernization, software-engineering
has_wikino
homepagehttps://www.modonome.com/
docs_sitehttps://www.modonome.com/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

53Moderate · 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 — no data
0.5/2.5CII-Best-Practices — badge detected: InProgress
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
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
0/7.5Maintained — project was created within the last 90 days. Please review its contents carefully
5/5Packaging — packaging workflow detected
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
5/5SAST — SAST tool detected: CodeQL
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 13 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.8
Excluded from scoring (no data or not applicable): CI-Tests, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: js-yaml 4.3.0 (high 7.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories16
affected_packages9
assessed_packages150
unassessed_packages2
affected_by_severitycritical 1, high 6, moderate 2
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 150 resolved dependencies against OSV. 2 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.

83Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md, docs/agents.md
15/15Machine-readable docs (llms.txt) — llms.txt present
40/40Legible commit history — 81 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share0.844
agent_instruction_filesAGENTS.md, CLAUDE.md, docs/agents.md
agent_instruction_max_bytes25,283
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — apps/control-panel/tsconfig.json, design-system/tsconfig.json, examples/node-typescript/tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 4 of the last 100 commits are automated dependency updates
2/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsapps/control-panel/tsconfig.json, design-system/tsconfig.json, examples/node-typescript/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.04
How it's scored
27/45Type-checkable code — JavaScript with type-check config (apps/control-panel/tsconfig.json, design-system/tsconfig.json, examples/node-typescript/tsconfig.json)
54.9/55Manageable file sizes — 1/541 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes65,462
source_files_sampled541
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

1GitHub stars
2contributors
141commits, last 12 months
6days since last push
1releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'modonome' points at a different repository (https://github.com/nateshpp/modonome); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 4.8 / 10
4.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-11 12:47 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
n/aCI-Testsno pull request found
2CII-Best-Practicesbadge detected: InProgress
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
10Packagingpackaging workflow detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
10SASTSAST tool detected: CodeQL
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities13 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmjs-yaml^4.3.0apps/control-panel/package.json
npmreact^18.3.1apps/control-panel/package.json
npmreact-dom^18.3.1apps/control-panel/package.json
All dependencies 152

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

RegistryPackageVersionRelation
npmjs-yaml4.3.0direct
npmreact18.3.1direct
npmreact-dom18.3.1direct
npm@babel/code-frame7.29.7indirect
npm@babel/compat-data7.29.7indirect
npm@babel/core7.29.7indirect
npm@babel/generator7.29.7indirect
npm@babel/helper-compilation-targets7.29.7indirect
npm@babel/helper-globals7.29.7indirect
npm@babel/helper-module-imports7.29.7indirect
npm@babel/helper-module-transforms7.29.7indirect
npm@babel/helper-plugin-utils7.29.7indirect
npm@babel/helper-string-parser7.29.7indirect
npm@babel/helper-validator-identifier7.29.7indirect
npm@babel/helper-validator-option7.29.7indirect
npm@babel/helpers7.29.7indirect
npm@babel/parser7.29.7indirect
npm@babel/plugin-transform-react-jsx-self7.29.7indirect
npm@babel/plugin-transform-react-jsx-source7.29.7indirect
npm@babel/template7.29.7indirect
npm@babel/traverse7.29.7indirect
npm@babel/types7.29.7indirect
npm@esbuild/aix-ppc640.21.5indirect
npm@esbuild/aix-ppc640.24.2indirect
npm@esbuild/android-arm0.21.5indirect
npm@esbuild/android-arm0.24.2indirect
npm@esbuild/android-arm640.21.5indirect
npm@esbuild/android-arm640.24.2indirect
npm@esbuild/android-x640.21.5indirect
npm@esbuild/android-x640.24.2indirect
npm@esbuild/darwin-arm640.21.5indirect
npm@esbuild/darwin-arm640.24.2indirect
npm@esbuild/darwin-x640.21.5indirect
npm@esbuild/darwin-x640.24.2indirect
npm@esbuild/freebsd-arm640.21.5indirect
npm@esbuild/freebsd-arm640.24.2indirect
npm@esbuild/freebsd-x640.21.5indirect
npm@esbuild/freebsd-x640.24.2indirect
npm@esbuild/linux-arm0.21.5indirect
npm@esbuild/linux-arm0.24.2indirect
npm@esbuild/linux-arm640.21.5indirect
npm@esbuild/linux-arm640.24.2indirect
npm@esbuild/linux-ia320.21.5indirect
npm@esbuild/linux-ia320.24.2indirect
npm@esbuild/linux-loong640.21.5indirect
npm@esbuild/linux-loong640.24.2indirect
npm@esbuild/linux-mips64el0.21.5indirect
npm@esbuild/linux-mips64el0.24.2indirect
npm@esbuild/linux-ppc640.21.5indirect
npm@esbuild/linux-ppc640.24.2indirect
npm@esbuild/linux-riscv640.21.5indirect
npm@esbuild/linux-riscv640.24.2indirect
npm@esbuild/linux-s390x0.21.5indirect
npm@esbuild/linux-s390x0.24.2indirect
npm@esbuild/linux-x640.21.5indirect
npm@esbuild/linux-x640.24.2indirect
npm@esbuild/netbsd-arm640.24.2indirect
npm@esbuild/netbsd-x640.21.5indirect
npm@esbuild/netbsd-x640.24.2indirect
npm@esbuild/openbsd-arm640.24.2indirect
npm@esbuild/openbsd-x640.21.5indirect
npm@esbuild/openbsd-x640.24.2indirect
npm@esbuild/sunos-x640.21.5indirect
npm@esbuild/sunos-x640.24.2indirect
npm@esbuild/win32-arm640.21.5indirect
npm@esbuild/win32-arm640.24.2indirect
npm@esbuild/win32-ia320.21.5indirect
npm@esbuild/win32-ia320.24.2indirect
npm@esbuild/win32-x640.21.5indirect
npm@esbuild/win32-x640.24.2indirect
npm@jridgewell/gen-mapping0.3.13indirect
npm@jridgewell/remapping2.3.5indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@rolldown/pluginutils1.0.0-beta.27indirect
npm@rollup/rollup-android-arm-eabi4.62.2indirect
npm@rollup/rollup-android-arm644.62.2indirect
npm@rollup/rollup-darwin-arm644.62.2indirect
npm@rollup/rollup-darwin-x644.62.2indirect
npm@rollup/rollup-freebsd-arm644.62.2indirect
npm@rollup/rollup-freebsd-x644.62.2indirect
npm@rollup/rollup-linux-arm-gnueabihf4.62.2indirect
npm@rollup/rollup-linux-arm-musleabihf4.62.2indirect
npm@rollup/rollup-linux-arm64-gnu4.62.2indirect
npm@rollup/rollup-linux-arm64-musl4.62.2indirect
npm@rollup/rollup-linux-loong64-gnu4.62.2indirect
npm@rollup/rollup-linux-loong64-musl4.62.2indirect
npm@rollup/rollup-linux-ppc64-gnu4.62.2indirect
npm@rollup/rollup-linux-ppc64-musl4.62.2indirect
npm@rollup/rollup-linux-riscv64-gnu4.62.2indirect
npm@rollup/rollup-linux-riscv64-musl4.62.2indirect
npm@rollup/rollup-linux-s390x-gnu4.62.2indirect
npm@rollup/rollup-linux-x64-gnu4.62.2indirect
npm@rollup/rollup-linux-x64-musl4.62.2indirect
npm@rollup/rollup-openbsd-x644.62.2indirect
npm@rollup/rollup-openharmony-arm644.62.2indirect
npm@rollup/rollup-win32-arm64-msvc4.62.2indirect
npm@rollup/rollup-win32-ia32-msvc4.62.2indirect
npm@rollup/rollup-win32-x64-gnu4.62.2indirect
npm@rollup/rollup-win32-x64-msvc4.62.2indirect
npm@types/babel__core7.20.5indirect
npm@types/babel__generator7.27.0indirect
npm@types/babel__template7.4.4indirect
npm@types/babel__traverse7.28.0indirect
npm@types/estree1.0.9indirect
npm@types/node20.10.6indirect
npm@types/node20.19.43indirect
npm@types/prop-types15.7.15indirect
npm@types/react18.3.31indirect
npm@types/react-dom18.3.7indirect
npm@typescript-eslint/eslint-plugin6.17.0indirect
npm@typescript-eslint/parser6.17.0indirect
npm@vitejs/plugin-react4.7.0indirect
npmargparse2.0.1indirect
npmbaseline-browser-mapping2.10.40indirect
npmbrowserslist4.28.4indirect
npmcaniuse-lite1.0.30001800indirect
npmconvert-source-map2.0.0indirect
npmcsstype3.2.3indirect
npmdebug4.4.3indirect
npmelectron-to-chromium1.5.383indirect
npmesbuild0.21.5indirect
npmesbuild0.24.2indirect
npmescalade3.2.0indirect
npmeslint8.56.0indirect
npmfsevents2.3.3indirect
npmgensync1.0.0-beta.2indirect
npmjs-tokens4.0.0indirect
npmjsesc3.1.0indirect
npmjson52.2.3indirect
npmloose-envify1.4.0indirect
npmlru-cache5.1.1indirect
npmms2.1.3indirect
npmnanoid3.3.15indirect
npmnode-releases2.0.50indirect
npmpicocolors1.1.1indirect
npmpostcss8.5.16indirect
npmreact-refresh0.17.0indirect
npmrollup4.62.2indirect
npmscheduler0.23.2indirect
npmsemver6.3.1indirect
npmsource-map-js1.2.1indirect
npmtypescript5.3.3indirect
npmtypescript5.9.3indirect
npmundici-types6.21.0indirect
npmupdate-browserslist-db1.2.3indirect
npmvite5.4.21indirect
npmvitest1.1.0indirect
npmyallist3.1.1indirect
PyPIpytest—indirect
PyPIruff—indirect
Dependency advisories 9

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

PackageVersionRelationSeverityAdvisoriesFixed in
vitest1.1.0indirectcritical24.1.0
js-yaml4.3.0directhigh24.3.2
baseline-browser-mapping2.10.40indirecthigh12.11.0
browserslist4.28.4indirecthigh24.28.7
nanoid3.3.15indirecthigh25.1.16
postcss8.5.16indirecthigh28.5.23
vite5.4.21indirecthigh38.0.16
esbuild0.21.5indirectmoderate10.25.0
esbuild0.24.2indirectmoderate10.25.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 — npm.