Public record
Software health reportschema 0.26.0 · metrics 2.10.0 · 2026-07-22 20:26 UTC

victoriadrake / hugo-theme-introduction

Minimal, single page, smooth-scrolling theme for Hugo static site generator.

HTMLApache-2.0★ 716 stars⑂ 269 forkssince Mar 2017View on GitHub ↗

victoriadrake/hugo-theme-introduction holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (71/100) and lowest on AI Readiness (26/100). It was last updated 32 days ago. 2 contributors account 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

Victoria DrakePersonal account
1,352 followers31 public repossince Dec 2016

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?

56Moderate · 21% of overall
How it's scored
18/36Push recencylast push 32 days ago
0.7/36Commit cadence1/52 weeks with commits
9.4/18Commit volume10 commits in the last year
10/10OpenSSF Scorecard: Maintained10 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year10
human_commit_share0.98
days_since_last_push32
active_weeks_last_year1
How it's scored
27/27Ships releases23 releases published
36/36Release recencylatest release 32 days ago
12.6/27Release cadencea release every ~315.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count23
latest_release_tagv6.0.3
releases_from_tagsno
days_since_latest_release32
mean_days_between_releases315.1
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?

71Good · 17% of overall
How it's scored
46.3/60Stars716 stars
20.2/25Forks269 forks
4.3/15Watchers7 watchers
Inputs used
forks269
stars716
watchers7
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_badges
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?

69Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.5/22.5Commit distributiontop contributor authored 44% of commits
13.5/13.5Contributor breadth45 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor2
contributors_sampled45
top_contributor_share0.444
How it's scored
42/42Issue resolution100% of issues closed
21.8/30PR acceptance130/179 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 10/28 approved changesets -- score normalized to 3
Inputs used
merged_prs130
open_issues0
closed_issues195
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs49
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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
22.5/25Owner reach1,352 followers of victoriadrake
23/25Track record31 public repos, account ~9 yr old
Inputs used
followers1,352
owner_typeUser
is_verified
owner_loginvictoriadrake
public_repos31
account_age_days3,502
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

40Weak · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests1 out of 13 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://hugo-introduction.netlify.app/
10/10Repository description
10/10Topics10 topics
0/10Wiki
Inputs used
topicshugo, theme, light, personal-website, blog-theme, hugo-theme, hugo-blog-theme, smooth-scrolling, language-translation, postcss
has_wikino
homepagehttps://hugo-introduction.netlify.app/
docs_sitehttps://hugo-introduction.netlify.app/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

59Moderate · 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-Tests1 out of 13 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 10/28 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
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.5Maintained10 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
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
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.9
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
advisories2
affected_packages2
assessed_packages74
unassessed_packages0
affected_by_severitymoderate 2
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 74 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.

26At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
28.3/40Legible commit history52 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.531
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
4/10Demonstrated agent practice2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance2 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.02
toolchain_manifests
dependency_bot_commit_share0.02
How it's scored
0/45Type-checkable codeHTML without a type-check config
33/55Manageable file sizes2/5 source files over 60KB
Inputs used
primary_languageHTML
largest_source_bytes90,596
source_files_sampled5
oversized_source_files2

Key facts

716GitHub stars
45contributors
10commits, last 12 months
32days since last push
23releases
2bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'hugo-theme-introduction' from its registry

More detail

Star and fork history 0 ★ / 269 ⇿
0Stars
269Forks
21Releases

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.

05010015020025030026652017-032021-082026-02
Major 2Minor 4Patch 6

Each point covers 9 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-22 20:25 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests1 out of 13 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 10/28 approved changesets -- score normalized to 3
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained10 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
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
8Vulnerabilities2 existing vulnerabilities detected
All dependencies 74

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

RegistryPackageVersionRelation
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmanymatch3.1.2indirect
npmarray-union3.0.1indirect
npmautoprefixer10.4.2indirect
npmbinary-extensions2.2.0indirect
npmbraces3.0.3indirect
npmbrowserslist4.19.1indirect
npmcaniuse-lite1.0.30001311indirect
npmchokidar3.5.3indirect
npmcliui7.0.4indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmdependency-graph0.11.0indirect
npmdir-glob3.0.1indirect
npmelectron-to-chromium1.4.68indirect
npmemoji-regex8.0.0indirect
npmescalade3.1.1indirect
npmfast-glob3.2.11indirect
npmfastq1.13.0indirect
npmfill-range7.1.1indirect
npmfraction.js4.1.3indirect
npmfs-extra10.0.0indirect
npmfsevents2.3.2indirect
npmget-caller-file2.0.5indirect
npmget-stdin9.0.0indirect
npmglob-parent5.1.2indirect
npmglobby12.2.0indirect
npmgraceful-fs4.2.9indirect
npmignore5.2.0indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmjsonfile6.1.0indirect
npmlilconfig2.0.4indirect
npmmerge21.4.1indirect
npmmicromatch4.0.4indirect
npmnanoid3.3.13indirect
npmnode-releases2.0.2indirect
npmnormalize-path3.0.0indirect
npmnormalize-range0.1.2indirect
npmpath-type4.0.0indirect
npmpicocolors1.1.1indirect
npmpicomatch2.3.2indirect
npmpify2.3.0indirect
npmpostcss8.5.10indirect
npmpostcss-cli9.1.0indirect
npmpostcss-load-config3.1.3indirect
npmpostcss-reporter7.0.5indirect
npmpostcss-value-parser4.2.0indirect
npmpretty-hrtime1.0.3indirect
npmqueue-microtask1.2.3indirect
npmread-cache1.0.0indirect
npmreaddirp3.6.0indirect
npmrequire-directory2.1.1indirect
npmreusify1.0.4indirect
npmrun-parallel1.2.0indirect
npmslash4.0.0indirect
npmsource-map-js1.2.1indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmthenby1.3.4indirect
npmto-regex-range5.0.1indirect
npmuniversalify2.0.0indirect
npmwrap-ansi7.0.0indirect
npmy18n5.0.8indirect
npmyaml1.10.2indirect
npmyargs17.3.1indirect
npmyargs-parser21.0.0indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
micromatch4.0.4indirectmoderate14.0.8
yaml1.10.2indirectmoderate12.8.3

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

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