Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-23 10:54 UTC

everfu / hexo-theme-solitude

一款设计师风格的 Hexo 主题,支持懒加载、PWA、Latex以及多种评论系统。

Stylus · JavaScript · PugApache-2.0★ 1,170 stars⑂ 114 forkssince Oct 2023View on GitHub ↗

everfu/hexo-theme-solitude holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (79/100) and lowest on AI Readiness (33/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

伍拾柒Personal account
48 followers26 public repossince Nov 2020undefined

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
npmhexo-theme-solitude4.0.02,3141385 days agohexothemesolitudecard-ui-designeverfuhexo-theme-solitude

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
9/36Commit cadence13/52 weeks with commits
16/18Commit volume60 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_year60
human_commit_share0.99
days_since_last_push1
active_weeks_last_year13
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 9 days ago
19.8/27Release cadencea release every ~56.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv4.0.0
releases_from_tagsno
days_since_latest_release9
mean_days_between_releases56.6
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
49.8/60Stars1,170 stars
17.1/25Forks114 forks
6.4/15Watchers15 watchers
Inputs used
forks114
stars1,170
watchers15
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
44.9/80Monthly downloads2,314 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageshexo-theme-solitude
dependents
ecosystemsnpm
total_downloads
monthly_downloads2,314
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?

65Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.5/22.5Commit distributiontop contributor authored 84% of commits
13.5/13.5Contributor breadth23 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled23
top_contributor_share0.845
How it's scored
42/42Issue resolution100% of issues closed
27.7/30PR acceptance355/385 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_prs355
open_issues0
closed_issues204
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs30
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
12.2/25Owner reach48 followers of everfu
21.8/25Track record26 public repos, account ~5 yr old
Inputs used
followers48
owner_typeUser
is_verified
owner_logineverfu
public_repos26
account_age_days2,078
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 5 days ago
20/20Version history138 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageshexo-theme-solitude
ecosystemsnpm
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 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-Testsno data
Inputs used
has_ciyes
has_testsno
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
0/25Documentation directory
15/15Documentation / homepage sitehttps://solitude.js.org
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicshexo, hexo-theme, hexo-theme-solitude, design, heo, simple, pjax, pwa
has_wikino
homepagehttps://solitude.js.org
docs_sitehttps://solitude.js.org
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

63Moderate · 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
2.5/2.5Contributorsproject has 11 contributing companies or organizations
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 0 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/5SASTno SAST tool detected
5/5Security-Policysecurity policy file 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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.4
Excluded from scoring (no data or not applicable): CI-Tests, 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_packages1
assessed_packages71
unassessed_packages0
affected_by_severityhigh 1
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 71 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.

33At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
39.3/40Legible commit history73 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.737
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
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance1 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.01
toolchain_manifests
dependency_bot_commit_share0.01
How it's scored
0/45Type-checkable codeStylus without a type-check config
55/55Manageable file sizes0/41 source files over 60KB
Inputs used
primary_languageStylus
largest_source_bytes54,051
source_files_sampled41
oversized_source_files0

Key facts

1,170GitHub stars
23contributors
60commits, last 12 months
1days since last push
100releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index npm:hexo-theme-solitude@4.0.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 114 ⇿
0Stars
114Forks
99Releases

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.

02040608010012011432023-112025-032026-06
Major 1Minor 6Patch 90

Each point covers 3 days.

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-23 10:54 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
10Contributorsproject has 11 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 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
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmhexo-renderer-pug^3.0.0package.json
npmhexo-renderer-stylus^3.0.0package.json
All dependencies 71

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

RegistryPackageVersionRelation
npmhexo-renderer-pug3.0.0direct
npmhexo-renderer-stylus3.0.1direct
npm@adobe/css-tools4.3.3indirect
npm@babel/helper-string-parser7.27.1indirect
npm@babel/helper-validator-identifier7.27.1indirect
npm@babel/parser7.28.0indirect
npm@babel/types7.28.1indirect
npmacorn7.4.1indirect
npmasap2.0.6indirect
npmassert-never1.4.0indirect
npmbabel-walk3.0.0-canary-5indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.12indirect
npmcall-bind-apply-helpers1.0.2indirect
npmcall-bound1.0.4indirect
npmcharacter-parser2.2.0indirect
npmconcat-map0.0.1indirect
npmconstantinople4.0.1indirect
npmdebug4.4.1indirect
npmdoctypes1.1.0indirect
npmdunder-proto1.0.1indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.1indirect
npmfs.realpath1.0.0indirect
npmfunction-bind1.1.2indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmglob7.2.3indirect
npmgopd1.2.0indirect
npmhas-symbols1.1.0indirect
npmhas-tostringtag1.0.2indirect
npmhasown2.0.2indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-core-module2.16.1indirect
npmis-expression4.0.0indirect
npmis-promise2.2.2indirect
npmis-regex1.2.1indirect
npmjs-stringify1.0.2indirect
npmjstransformer1.0.0indirect
npmmath-intrinsics1.1.0indirect
npmminimatch3.1.4indirect
npmms2.1.3indirect
npmnib1.2.0indirect
npmobject-assign4.1.1indirect
npmonce1.4.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-parse1.0.7indirect
npmpromise7.3.1indirect
npmpug3.0.3indirect
npmpug-attrs3.0.0indirect
npmpug-code-gen3.0.3indirect
npmpug-error2.1.0indirect
npmpug-filters4.0.0indirect
npmpug-lexer5.0.1indirect
npmpug-linker4.0.0indirect
npmpug-load3.0.0indirect
npmpug-parser6.0.0indirect
npmpug-runtime3.0.1indirect
npmpug-strip-comments2.0.0indirect
npmpug-walk2.0.0indirect
npmresolve1.22.10indirect
npmsax1.3.0indirect
npmsource-map0.7.4indirect
npmstylus0.62.0indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmtoken-stream1.0.0indirect
npmvoid-elements3.1.0indirect
npmwith7.0.2indirect
npmwrappy1.0.2indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion1.1.12indirecthigh25.0.7

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

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