Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 17:47 UTC

docsy / docsy-example

An example documentation site using the Docsy Hugo theme

JavaScriptApache-2.0★ 558 stars⑂ 753 forkssince Oct 2018View on GitHub ↗
KindNetwork servicehow this is determined

docsy/docsy-example holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (83/100) and lowest on Sustainability & Governance (54/100). It was last updated today. 2 contributors account for most of its recent work.

86
overall / 100
Excellent

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.

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

Ownership

DocsyOrganization
1 follower3 public repossince Aug 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/google/docsy-examplepoints to another repo — not scoredv0.17.0-1819 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
14.5/36Commit cadence21/52 weeks with commits
16.3/18Commit volume64 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year64
human_commit_share0.7
days_since_last_push0
active_weeks_last_year21
How it's scored
27/27Ships releases18 releases published
36/36Release recencylatest release 19 days ago
19.8/27Release cadencea release every ~94.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count18
latest_release_tagv0.17.0
releases_from_tagsno
days_since_latest_release19
mean_days_between_releases94.5
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?

73Good · 17% of overall
How it's scored
44.5/60Stars558 stars
24/25Forks753 forks
7/15Watchers19 watchers
Inputs used
forks753
stars558
watchers19
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

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
25.2/54Bus factor2 contributor(s) cover half of all commits
12/22.5Commit distributiontop contributor authored 47% of commits
13.5/13.5Contributor breadth33 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor2
contributors_sampled33
top_contributor_share0.466
How it's scored
39.2/42Issue resolution93% of issues closed
20.1/30PR acceptance246/368 decided PRs merged
5.2/13Newcomer PR acceptance2/5 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/27 approved changesets -- score normalized to 1
Inputs used
merged_prs246
open_issues8
closed_issues111
prs_merged_7d2
prs_decided_7d4
prs_merged_30d16
prs_decided_30d21
issue_closed_ratio0.933
closed_unmerged_prs122
first_time_authors_30d3
first_time_prs_merged_30d2
first_time_prs_decided_30d5
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
2.2/25Owner reach1 followers of docsy
4.5/25Track record3 public repos, account ~0 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedno
owner_logindocsy
public_repos3
account_age_days18

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configpackage.json ("prettier")
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://example.docsy.dev
10/10Repository description
10/10Topics8 topics
10/10Wiki
Inputs used
topicsdocsy, hugo, hugo-theme, documentation-site, documentation-website, docker, docsy-example, hugo-theme-demo
has_wikiyes
homepagehttps://example.docsy.dev
docs_sitehttps://example.docsy.dev
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

73Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 3/27 approved changesets -- score normalized to 1
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
5/5Pinned-Dependenciesall dependencies are pinned
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
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.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
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages135
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 135 resolved dependencies against OSV. 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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://www.docsy.dev/llms.txt)
40/40Legible commit history63 of 70 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://www.docsy.dev/llms.txt
legible_history_share0.9
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapgo.mod (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format configpackage.json ("prettier")
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance30 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, package-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share0.3
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/4 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes2,254
source_files_sampled4
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

558GitHub stars
33contributors
64commits, last 12 months
0days since last push
18releases
2bus factor
8open issues
Go, npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 753 ⇿
0Stars
753Forks
18Releases

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.

0125250375500625750675142018-102022-092026-09
Major 0Minor 11Patch 7

Each point covers 8 days.

OpenSSF Scorecard 6.5 / 10
6.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-09-19 17:46 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 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 3/27 approved changesets -- score normalized to 1
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npm@fortawesome/fontawesome-free7.3.1packages/hugoautogen/package.json
npmbootstrap5.3.8packages/hugoautogen/package.json
All dependencies 135

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

RegistryPackageVersionRelation
npm@fortawesome/fontawesome-free7.3.1direct
npmbootstrap5.3.8direct
Gogithub.com/google/docsy/themev0.17.1-0.20260831231032-2c44726e7773indirect
npm@bufbuild/protobuf2.14.0indirect
npm@docsy/hugoautogen0.1.0indirect
npm@epic-web/invariant1.0.0indirect
npm@isaacs/fs-minipass4.0.1indirect
npm@parcel/watcher2.6.0indirect
npm@parcel/watcher-android-arm642.6.0indirect
npm@parcel/watcher-darwin-arm642.6.0indirect
npm@parcel/watcher-darwin-x642.6.0indirect
npm@parcel/watcher-freebsd-x642.6.0indirect
npm@parcel/watcher-linux-arm-glibc2.6.0indirect
npm@parcel/watcher-linux-arm-musl2.6.0indirect
npm@parcel/watcher-linux-arm64-glibc2.6.0indirect
npm@parcel/watcher-linux-arm64-musl2.6.0indirect
npm@parcel/watcher-linux-x64-glibc2.6.0indirect
npm@parcel/watcher-linux-x64-musl2.6.0indirect
npm@parcel/watcher-win32-arm642.6.0indirect
npm@parcel/watcher-win32-x642.6.0indirect
npm@popperjs/core2.11.8indirect
npmadm-zip0.6.1indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmanymatch3.1.3indirect
npmautoprefixer10.5.4indirect
npmbaseline-browser-mapping2.11.15indirect
npmbinary-extensions2.3.0indirect
npmbraces3.0.3indirect
npmbrowserslist4.28.8indirect
npmcaniuse-lite1.0.30001809indirect
npmchokidar3.6.0indirect
npmchokidar5.0.0indirect
npmchownr3.0.0indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcolorjs.io0.7.1indirect
npmcross-env10.1.0indirect
npmcross-spawn7.0.6indirect
npmdependency-graph1.0.0indirect
npmdetect-libc2.1.2indirect
npmelectron-to-chromium1.5.409indirect
npmemoji-regex8.0.0indirect
npmescalade3.2.0indirect
npmfdir6.5.0indirect
npmfill-range7.1.1indirect
npmfraction.js5.3.4indirect
npmfs-extra11.4.0indirect
npmfsevents2.3.3indirect
npmget-caller-file2.0.5indirect
npmglob-parent5.1.2indirect
npmgraceful-fs4.2.11indirect
npmhas-flag4.0.0indirect
npmhugo-extended0.164.0indirect
npmimmutable5.1.9indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmisexe2.0.0indirect
npmjsonfile6.2.1indirect
npmlilconfig3.1.3indirect
npmlink-cache0.3.0indirect
npmminipass7.1.3indirect
npmminizlib3.1.0indirect
npmnanoid3.3.18indirect
npmnode-addon-api7.1.1indirect
npmnode-releases2.0.53indirect
npmnormalize-path3.0.0indirect
npmnpm-check-updates23.1.0indirect
npmpath-key3.1.1indirect
npmpicocolors1.1.1indirect
npmpicomatch2.3.2indirect
npmpicomatch4.0.5indirect
npmpify2.3.0indirect
npmpostcss8.5.26indirect
npmpostcss-cli11.0.1indirect
npmpostcss-load-config5.1.0indirect
npmpostcss-reporter7.1.0indirect
npmpostcss-value-parser4.2.0indirect
npmprettier3.9.6indirect
npmpretty-hrtime1.0.3indirect
npmread-cache1.0.0indirect
npmreaddirp3.6.0indirect
npmreaddirp5.1.1indirect
npmrequire-directory2.1.1indirect
npmrtlcss4.3.0indirect
npmrxjs7.8.2indirect
npmsass1.103.1indirect
npmsass-embedded1.103.1indirect
npmsass-embedded-all-unknown1.103.1indirect
npmsass-embedded-android-arm1.103.1indirect
npmsass-embedded-android-arm641.103.1indirect
npmsass-embedded-android-riscv641.103.1indirect
npmsass-embedded-android-x641.103.1indirect
npmsass-embedded-darwin-arm641.103.1indirect
npmsass-embedded-darwin-x641.103.1indirect
npmsass-embedded-linux-arm1.103.1indirect
npmsass-embedded-linux-arm641.103.1indirect
npmsass-embedded-linux-musl-arm1.103.1indirect
npmsass-embedded-linux-musl-arm641.103.1indirect
npmsass-embedded-linux-musl-riscv641.103.1indirect
npmsass-embedded-linux-musl-x641.103.1indirect
npmsass-embedded-linux-riscv641.103.1indirect
npmsass-embedded-linux-x641.103.1indirect
npmsass-embedded-unknown-all1.103.1indirect
npmsass-embedded-win32-arm641.103.1indirect
npmsass-embedded-win32-x641.103.1indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmslash5.1.0indirect
npmsource-map-js1.2.1indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color8.1.1indirect
npmsync-child-process1.0.2indirect
npmsync-message-port1.2.0indirect
npmtar7.5.22indirect
npmthenby1.4.1indirect
npmtinyglobby0.2.17indirect
npmto-regex-range5.0.1indirect
npmtslib2.8.1indirect
npmuniversalify2.0.1indirect
npmupdate-browserslist-db1.3.1indirect
npmvarint6.0.0indirect
npmwhich2.0.2indirect
npmwrap-ansi7.0.0indirect
npmy18n5.0.8indirect
npmyallist5.0.0indirect
npmyaml2.9.0indirect
npmyargs17.7.3indirect
npmyargs-parser21.1.1indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 135 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

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

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