Public record
Software health reportschema 0.30.0 · metrics 2.10.0 · 2026-08-04 16:19 UTC

lukasgeiter / mkdocs-awesome-nav

A plugin for customizing the navigation structure of your MkDocs site.

PythonMIT★ 625 stars⑂ 42 forkssince Feb 2018View on GitHub ↗
KindPluginLibraryhow this is determined

lukasgeiter/mkdocs-awesome-nav holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (78/100) and lowest on Vitality (38/100). It was last updated 116 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Lukas GeiterPersonal account
25 followers8 public repossince Nov 2013

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
PyPImkdocs-awesome-nav3.3.01,131,4816244 days agomkdocsmarkdowndocumentationnavigation

Metrics by category

Vitality

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

38Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 116 days ago
2.1/36Commit cadence3/52 weeks with commits
5.4/18Commit volume3 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year3
human_commit_share1
days_since_last_push116
active_weeks_last_year3
How it's scored
27/27Ships releases33 releases published
16.2/36Release recencylatest release 244 days ago
19.8/27Release cadencea release every ~92.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count33
latest_release_tagv3.3.0
releases_from_tagsno
days_since_latest_release244
mean_days_between_releases92.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?

68Good · 17% of overall
How it's scored
45.3/60Stars625 stars
13.4/25Forks42 forks
4.7/15Watchers8 watchers
Inputs used
forks42
stars625
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Monthly downloads1,131,481 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmkdocs-awesome-nav
dependents
ecosystemspypi
total_downloads
monthly_downloads1,131,481
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?

54Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.2/22.5Commit distributiontop contributor authored 86% of commits
13.5/13.5Contributor breadth12 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.858
How it's scored
34.2/42Issue resolution82% of issues closed
15/30PR acceptance13/26 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 6/30 approved changesets -- score normalized to 2
Inputs used
merged_prs13
open_issues22
closed_issues97
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.815
closed_unmerged_prs13
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
10.2/25Owner reach25 followers of lukasgeiter
18.9/25Track record8 public repos, account ~12 yr old
Inputs used
followers25
owner_typeUser
is_verified
owner_loginlukasgeiter
public_repos8
account_age_days4,649
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on pypi
26/35Publish recencylatest publish 244 days ago
20/20Version history6 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmkdocs-awesome-nav
ecosystemspypi
any_deprecatedno
min_days_since_publish244

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configtox.ini
0/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests2 out of 6 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://lukasgeiter.github.io/mkdocs-awesome-nav/
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsmkdocs, python, markdown, wiki
has_wikino
homepagehttps://lukasgeiter.github.io/mkdocs-awesome-nav/
docs_sitehttps://lukasgeiter.github.io/mkdocs-awesome-nav/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

40Weak · 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.8/2.5CI-Tests2 out of 6 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 6/30 approved changesets -- score normalized to 2
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities27 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.5
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages24
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:mkdocs-awesome-nav@3.3.0 runtime dependency closure — what installing the published package pulls in — 24 packages. 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.

42Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
3.7/40Legible commit history7 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.07
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configtox.ini
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
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_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/52 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes8,535
source_files_sampled52
oversized_source_files0
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

625GitHub stars
12contributors
3commits, last 12 months
116days since last push
33releases
1bus factor
22open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 42 ⇿
0Stars
42Forks
24Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

010203040504212019-032022-102026-05
Major 1Minor 13Patch 10

Each point covers 7 days.

OpenSSF Scorecard 2.5 / 10
2.5aggregate

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-08-04 16:19 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
3CI-Tests2 out of 6 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 6/30 approved changesets -- score normalized to 2
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities27 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
PyPImkdocs>=1.6.0pyproject.toml
PyPInatsort>=8.1.0pyproject.toml
PyPIpydantic>=2.0.2pyproject.toml
PyPIpydantic>=2.8.1pyproject.toml
PyPIwcmatch>=8.4pyproject.toml
All dependencies 47

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

RegistryPackageVersionRelation
PyPImkdocs1.6.0direct
PyPInatsort8.1.0direct
PyPIwcmatch8.3direct
PyPIaiohttp3.8.4indirect
PyPIaiosignal1.2.0indirect
PyPIasync-timeout4.0.2indirect
PyPIattrs21.2.0indirect
PyPIbeautifulsoup44.12.3indirect
PyPIblack24.2.0indirect
PyPIbracex2.2.1indirect
PyPIcharset-normalizer2.0.9indirect
PyPIclick8.0.3indirect
PyPIcolorama0.4.4indirect
PyPIexceptiongroup1.2.0indirect
PyPIflake87.0.0indirect
PyPIfrozenlist1.3.3indirect
PyPIghp-import2.0.2indirect
PyPIidna3.3indirect
PyPIimportlib-metadata4.8.3indirect
PyPIiniconfig1.1.1indirect
PyPIisort5.13.2indirect
PyPIjinja23.0.3indirect
PyPImarkdown3.3.6indirect
PyPImarkupsafe2.0.1indirect
PyPImccabe0.7.0indirect
PyPImergedeep1.3.4indirect
PyPImkdocs-get-deps0.2.0indirect
PyPImock-open1.4.0indirect
PyPImultidict5.2.0indirect
PyPImypy-extensions0.4.3indirect
PyPIpackaging23.0indirect
PyPIpathspec0.12.1indirect
PyPIplatformdirs2.4.0indirect
PyPIpluggy1.4.0indirect
PyPIpycodestyle2.11.1indirect
PyPIpyflakes3.2.0indirect
PyPIpytest8.1.1indirect
PyPIpython-dateutil2.8.2indirect
PyPIpyyaml6.0indirect
PyPIpyyaml-env-tag0.1indirect
PyPIsix1.16.0indirect
PyPIsoupsieve2.3.1indirect
PyPItomli1.2.3indirect
PyPItyping-extensions4.0.1indirect
PyPIwatchdog2.1.6indirect
PyPIyarl1.8.2indirect
PyPIzipp3.6.0indirect
Dependency advisories 0

Installing pypi:mkdocs-awesome-nav@3.3.0 pulls in 24 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.30.0 — full methodology · metrics wiki.

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