Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 06:16 UTC

TryGhost / gscan

Ghost theme scanner - checks for errors and feature support

JavaScriptMIT★ 84 stars⑂ 60 forkssince Oct 2014View on GitHub ↗
KindNetwork serviceCommand-line toolLibraryhow this is determined

TryGhost/gscan holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (83/100) and lowest on Community & Adoption (59/100). It was last updated 1 day ago. 3 contributors account for most of its recent work.

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

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

Ownership

GhostOrganization · verified domain
1,755 followers154 public repossince Aug 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmgscan6.6.077,9532492 days agoghostthemesvalidatorlint

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
34.6/36Commit cadence — 50/52 weeks with commits
18/18Commit volume — 299 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year299
human_commit_share0.2
days_since_last_push1
active_weeks_last_year50
How it's scored
27/27Ships releases — 3 releases published
0/36Release recency — latest release 2,514 days ago
12.6/27Release cadence — a release every ~263.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv3.0.0
releases_from_tagsno
days_since_latest_release2,514
mean_days_between_releases263.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?

59Moderate · 17% of overall
How it's scored
31.1/60Stars — 84 stars
14.8/25Forks — 60 forks
6.8/15Watchers — 18 watchers
Inputs used
forks60
stars84
watchers18
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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
65.2/80Monthly downloads — 77,953 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesgscan
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads77,953
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?

83Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
16.4/22.5Commit distribution — top contributor authored 27% of commits
13.5/13.5Contributor breadth — 53 contributors
10/10OpenSSF Scorecard: Contributors — project has 18 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled53
top_contributor_share0.272
How it's scored
39.4/42Issue resolution — 94% of issues closed
24.7/30PR acceptance — 662/804 decided PRs merged
0/13Newcomer PR acceptance — 0/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/30 approved changesets -- score normalized to 0
Inputs used
merged_prs662
open_issues7
closed_issues104
prs_merged_7d2
prs_decided_7d4
prs_merged_30d8
prs_decided_30d12
issue_closed_ratio0.937
closed_unmerged_prs142
first_time_authors_30d2
first_time_prs_merged_30d0
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
23.3/25Owner reach — 1,755 followers of TryGhost
25/25Track record — 154 public repos, account ~14 yr old
Inputs used
followers1,755
owner_typeOrganization
is_verifiedyes
owner_loginTryGhost
public_repos154
account_age_days5,135

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 2 days ago
20/20Version history — 249 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgscan
ecosystemsnpm
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 28 out of 28 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://gscan.ghost.org
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://gscan.ghost.org
docs_sitehttps://gscan.ghost.org
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 28 out of 28 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 18 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
4/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.7
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
8.8/25Indirect dependencies free of known advisories — 1 affected: extract-zip 2.0.1 (high 8.1)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages83
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Matched the npm:gscan@6.6.0 runtime dependency closure — what installing the published package pulls in — 83 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.

70Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md, packages/gscan/test/fixtures/themes/theme-with-ai-tooling/AGENTS.md, packages/gscan/test/fixtures/themes/theme-with-ai-tooling/CLAUDE.md
0/15Machine-readable docs (llms.txt)
34.7/40Legible commit history — 13 of 20 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.65
agent_instruction_filesAGENTS.md, CLAUDE.md, packages/gscan/test/fixtures/themes/theme-with-ai-tooling/AGENTS.md, packages/gscan/test/fixtures/themes/theme-with-ai-tooling/CLAUDE.md
agent_instruction_max_bytes9,745
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — packages/gscan/jsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 80 of the last 100 commits are automated dependency updates
8/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configspackages/gscan/jsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.8
How it's scored
27/45Type-checkable code — JavaScript with type-check config (packages/gscan/jsconfig.json)
54.5/55Manageable file sizes — 1/116 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes189,449
source_files_sampled116
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — example
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

84GitHub stars
53contributors
299commits, last 12 months
1days since last push
3releases
3bus factor
7open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 60 ⇿
0Stars
60Forks
3Releases

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.

01020304050606032016-012021-042026-08
Major 2Minor 0Patch 1

Each point covers 10 days.

OpenSSF Scorecard 6.7 / 10
6.7aggregate

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-11 06:15 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests28 out of 28 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/30 approved changesets -- score normalized to 0
10Contributorsproject has 18 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 9 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 20
RegistryPackageVersion constraintManifest
npm@sentry/node10.73.0apps/web/package.json
npm@tryghost/config2.3.13apps/web/package.json
npm@tryghost/debug2.3.13apps/web/package.json
npm@tryghost/errors3.3.13apps/web/package.json
npm@tryghost/logging5.4.4apps/web/package.json
npm@tryghost/server3.1.14apps/web/package.json
npmexpress5.2.1apps/web/package.json
npmexpress-handlebars8.0.1apps/web/package.json
npmgscanworkspace:*apps/web/package.json
npmmulter2.3.0apps/web/package.json
npm@tryghost/debug2.3.13packages/gscan/package.json
npm@tryghost/errors3.3.13packages/gscan/package.json
npm@tryghost/nql0.13.4packages/gscan/package.json
npm@tryghost/pretty-cli3.3.13packages/gscan/package.json
npm@tryghost/zip3.5.12packages/gscan/package.json
npmchalk6.0.0packages/gscan/package.json
npmhandlebars4.7.9packages/gscan/package.json
npmlodash4.18.1packages/gscan/package.json
npmsemver7.8.5packages/gscan/package.json
npmvalidator^13.0.0packages/gscan/package.json
All dependencies 34

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

RegistryPackageVersionRelation
npm@sentry/node10.73.0direct
npm@tryghost/config2.3.13direct
npm@tryghost/debug2.3.13direct
npm@tryghost/errors3.3.13direct
npm@tryghost/logging5.4.4direct
npm@tryghost/nql0.13.4direct
npm@tryghost/pretty-cli3.3.13direct
npm@tryghost/server3.1.14direct
npm@tryghost/zip3.5.12direct
npmchalk6.0.0direct
npmexpress5.2.1direct
npmexpress-handlebars8.0.1direct
npmhandlebars4.7.9direct
npmlodash4.18.1direct
npmmulter2.3.0direct
npmsemver7.8.5direct
npmvalidator^13.0.0direct
npm@pnpm/exe.android-arm6412.4.0indirect
npm@pnpm/exe.android-x6412.4.0indirect
npm@pnpm/exe.darwin-arm6412.4.0indirect
npm@pnpm/exe.darwin-x6412.4.0indirect
npm@pnpm/exe.freebsd-x6412.4.0indirect
npm@pnpm/exe.linux-arm6412.4.0indirect
npm@pnpm/exe.linux-arm64-musl12.4.0indirect
npm@pnpm/exe.linux-ppc6412.4.0indirect
npm@pnpm/exe.linux-riscv6412.4.0indirect
npm@pnpm/exe.linux-s390x12.4.0indirect
npm@pnpm/exe.linux-x6412.4.0indirect
npm@pnpm/exe.linux-x64-musl12.4.0indirect
npm@pnpm/exe.win32-arm6412.4.0indirect
npm@pnpm/exe.win32-x6412.4.0indirect
npm@tryghost/pro-ship1.1.8indirect
npmnodemon3.1.14indirect
npmpnpm12.4.0indirect
Dependency advisories 1

Installing npm:gscan@6.6.0 pulls in 83 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
extract-zip2.0.1indirecthigh2—

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 statistics — npm.