Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-20 06:30 UTC

bekirdag / docdex

A document index with MCP, http and client support. https://docdex.org/

RustMIT★ 20 stars⑂ 2 forkssince Nov 2025View on GitHub ↗
KindTerminal interfaceCommand-line toolLibraryNetwork servicehow this is determined

bekirdag/docdex holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (85/100) and lowest on Community & Adoption (49/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

69
overall / 100
Good

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.

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

Ownership

Bekir DağPersonal account
9 followers37 public repossince Feb 2011piyote.com

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 publishTags
npmdocdex0.2.907,260903 days agodocdexdocumentationsearchindexcode-searchmcpaiagentragknowledge-basecli

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
18/36Commit cadence26/52 weeks with commits
18/18Commit volume891 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year891
human_commit_share
days_since_last_push3
active_weeks_last_year26
How it's scored
27/27Ships releases94 releases published
36/36Release recencylatest release 3 days ago
27/27Release cadencea release every ~3.3 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count94
latest_release_tagv0.2.90
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases3.3

Community & Adoption

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

49Weak · 17% of overall
How it's scored
20.7/60Stars20 stars
0/25Forks2 forks
0/15Watchers1 watchers
Inputs used
forks2
stars20
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
51.5/80Monthly downloads7,260 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesdocdex
dependents
ecosystemsnpm
total_downloads
monthly_downloads7,260
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?

53Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
2.7/13.5Contributor breadth2 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.999
How it's scored
0/42Issue resolutionno issues or no data
27.3/30PR acceptance10/11 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs10
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs1
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
7.2/25Owner reach9 followers of bekirdag
23.5/25Track record37 public repos, account ~15 yr old
Inputs used
followers9
owner_typeUser
is_verified
owner_loginbekirdag
public_repos37
account_age_days5,644
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 3 days ago
20/20Version history90 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesdocdex
ecosystemsnpm
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
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.
How it's scored
30/30README
25/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_diryes
has_descriptionyes

Security

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

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
3.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
3/7.5Vulnerabilities6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.2
Excluded from scoring (no data or not applicable): CI-Tests. 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.

64Moderate · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, npm/assets/agents.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesAGENTS.md, npm/assets/agents.md
agent_instruction_max_bytes40,244
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
7/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, package-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeRust (statically typed)
51.3/55Manageable file sizes30/449 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes405,081
source_files_sampled449
oversized_source_files30
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalyes
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

20GitHub stars
2contributors
891commits, last 12 months
3days since last push
94releases
1bus factor
0open issues
crates.io, npmpackage ecosystems

Data collection warnings

  • Could not fetch crates package 'docdexd' from its registry
  • Could not fetch crates package 'docdexd-fuzz' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 5.2 / 10
5.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-07-20 06:30 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
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
7Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 72
RegistryPackageVersion constraintManifest
crates.ioanyhow1.0Cargo.toml
crates.ioaxum0.7Cargo.toml
crates.ioclap4.5Cargo.toml
crates.iofutures0.3Cargo.toml
crates.iofs40.7Cargo.toml
crates.ioonce_cell1.19Cargo.toml
crates.ioparking_lot0.12Cargo.toml
crates.ioregex1.10Cargo.toml
crates.ioserde1.0Cargo.toml
crates.ioserde_json1.0Cargo.toml
crates.ioserde_urlencoded0.7Cargo.toml
crates.iotoml0.8Cargo.toml
crates.iotokio1.39Cargo.toml
crates.iotracing0.1Cargo.toml
crates.iotracing-subscriber0.3Cargo.toml
crates.iotantivy0.21Cargo.toml
crates.iowalkdir2.5Cargo.toml
crates.iothiserror1.0Cargo.toml
crates.iochrono0.4Cargo.toml
crates.iocrossterm0.27Cargo.toml
crates.ionotify6Cargo.toml
crates.iozstd-sys=2.0.9Cargo.toml
crates.ioipnet2Cargo.toml
crates.iorustls-pemfile2Cargo.toml
crates.iotokio-rustls0.26Cargo.toml
crates.iohyper-util0.1Cargo.toml
crates.iohyper1Cargo.toml
crates.iotower0.4Cargo.toml
crates.ioammonia3Cargo.toml
crates.ioaes-gcm0.10Cargo.toml
crates.iobase640.22Cargo.toml
crates.iohtml2text0.13Cargo.toml
crates.ionix0.29Cargo.toml
crates.iouuid1Cargo.toml
crates.iosha20.10Cargo.toml
crates.iohmac0.12Cargo.toml
crates.ioflate21.0Cargo.toml
crates.iohex0.4Cargo.toml
crates.iowhich6Cargo.toml
crates.iosysinfo0.30Cargo.toml
crates.iorusqlite0.31Cargo.toml
crates.ioratatui0.26Cargo.toml
crates.iozip0.6Cargo.toml
crates.iohttp-body-util0.1Cargo.toml
crates.ioreqwest0.12Cargo.toml
crates.iourl2.5Cargo.toml
crates.ioreadability0.3Cargo.toml
crates.iotempfile3.10Cargo.toml
crates.iotokio-tungstenite0.21Cargo.toml
crates.iotree-sitter0.22.6Cargo.toml
crates.iotree-sitter-go0.21.2Cargo.toml
crates.iotree-sitter-javascript0.21.4Cargo.toml
crates.iotree-sitter-python0.21.0Cargo.toml
crates.iotree-sitter-rust0.21.2Cargo.toml
crates.iotree-sitter-typescript0.21.2Cargo.toml
crates.iotree-sitter-java0.21.0Cargo.toml
crates.iotree-sitter-c-sharp0.21.3Cargo.toml
crates.iotree-sitter-c0.21.4Cargo.toml
crates.iotree-sitter-cpp0.22.3Cargo.toml
crates.iotree-sitter-php0.23.0Cargo.toml
crates.iotree-sitter-kotlin0.3.8Cargo.toml
crates.iotree-sitter-swift0.5.0Cargo.toml
crates.iotree-sitter-ruby0.21.0Cargo.toml
crates.iotree-sitter-lua0.1.0Cargo.toml
crates.iotree-sitter-dart0.0.4Cargo.toml
crates.iohdrhistogram7.5Cargo.toml
crates.ioignore0.4Cargo.toml
crates.iotokio-stream0.1Cargo.toml
crates.iolibfuzzer-sys0.4fuzz/Cargo.toml
crates.iodocdexdfuzz/Cargo.toml
crates.ioserde_json1.0fuzz/Cargo.toml
npmtar^7.5.19npm/package.json
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.15.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.