Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-19 04:49 UTC

reidransom / gojekyll

A fast Go implementation of the Jekyll blogging engine

GoMIT★ 0 stars⑂ 1 forksince Feb 2025forkView on GitHub ↗

reidransom/gojekyll holds a health index of 44 out of 100, placing it in the Weak band. It scores highest on Vitality (84/100) and lowest on Community & Adoption (12/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

44
overall / 100
Weak

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.

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

Ownership

Reid RansomPersonal account
16 followers65 public repossince Nov 2010Premiere Digital

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 publish
Gogithub.com/reidransom/jigyllpoints to another repo — not scoredv1.5.0-614 days ago

Metrics by category

Vitality

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

84Excellent · 21% of overall

Development activity

80Excellent
How it's scored
36/36Push recency — last push 4 days ago
15.9/36Commit cadence — 23/52 weeks with commits
18/18Commit volume — 123 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year123
human_commit_share—
days_since_last_push4
active_weeks_last_year23

Release discipline

90Excellent
How it's scored
27/27Ships releases — 36 releases published
36/36Release recency — latest release 4 days ago
27/27Release cadence — a release every ~4.5 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count36
latest_release_tagv1.5.0
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases4.5

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

12Critical · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 0 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

25At Risk
How it's scored
0/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_readmeno
has_licenseno
readme_badges—
has_contributingno
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?

30At Risk · 23% of overall

Maintainer resilience (bus factor)

34At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.6/22.5Commit distribution — top contributor authored 75% of commits
9.5/13.5Contributor breadth — 7 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.752

Issue & PR responsiveness

1Critical
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

55Moderate
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
8.8/25Owner reach — 16 followers of reidransom
25/25Track record — 65 public repos, account ~15 yr old
Inputs used
followers16
owner_typeUser
is_verified—
owner_loginreidransom
public_repos65
account_age_days5,734
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

58Moderate · 19% of overall

Engineering practices

80Excellent
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — .golangci.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

25At Risk
How it's scored
0/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

34At Risk · 16% of overall

Security posture

34At Risk
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 5 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0.8/7.5Vulnerabilities — 9 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): CI-Tests. Remaining weights renormalized.

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.

66Good · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

Verify loop (build / test / typecheck)

88Excellent
How it's scored
18/18One-command bootstrap — Makefile, justfile
22/22Automated tests
11/11Lint / format config — .golangci.yml
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile, justfile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share—
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — Go (statically typed)
55/55Manageable file sizes — 0/139 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes14,537
source_files_sampled139
oversized_source_files0

Machine-readable interfaces

100Exceptional
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — example
Inputs used
example_dirsexample
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

0GitHub stars
7contributors
123commits, last 12 months
4days since last push
36releases
1bus factor
0open issues
Go, RubyGemspackage ecosystems

Data collection warnings

  • Community profile unavailable
  • go package 'github.com/reidransom/jigyll' points at a different repository (https://github.com/reidransom/jigyll); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 3.4 / 10
3.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-19 04:48 UTC

9Binary-Artifactsbinaries present in source code
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 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update 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
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
1Vulnerabilities9 existing vulnerabilities detected
Direct dependencies 24
RegistryPackageVersion constraintManifest
RubyGemsjekyll-github-metadata—example/Gemfile
RubyGemsjekyll-avatar—example/Gemfile
RubyGemsjekyll-gist—example/Gemfile
Gogithub.com/alecthomas/chromav0.10.0go.mod
Gogithub.com/alecthomas/kingpin/v2v2.4.0go.mod
Gogithub.com/bep/godartsass/v2v2.5.0go.mod
Gogithub.com/fsnotify/fsnotifyv1.9.0go.mod
Gogithub.com/google/go-githubv17.0.0+incompatiblego.mod
Gogithub.com/jaschaephraim/lrserverv0.0.0-20240306232639-afed386b3640go.mod
Gogithub.com/k0kubun/ppv3.0.1+incompatiblego.mod
Gogithub.com/kyokomi/emojiv2.2.4+incompatiblego.mod
Gogithub.com/montanaflynn/statsv0.7.1go.mod
Gogithub.com/pkg/browserv0.0.0-20240102092130-5ac0b6a4141cgo.mod
Gogithub.com/radovskyb/watcherv1.0.7go.mod
Gogithub.com/stretchr/testifyv1.11.1go.mod
Gogithub.com/tdewolff/minifyv2.3.6+incompatiblego.mod
Gogithub.com/yuin/goldmarkv1.7.16go.mod
Gogithub.com/yuin/goldmark-highlightingv0.0.0-20220208100518-594be1970594go.mod
Gogolang.org/x/netv0.46.0go.mod
Gogolang.org/x/oauth2v0.30.0go.mod
Gogopkg.in/yaml.v2v2.4.0go.mod
Gogithub.com/gohugoio/hugo-goldmark-extensions/passthroughv0.3.1go.mod
Gogithub.com/bmatcuk/doublestar/v4v4.10.0go.mod
Gogithub.com/reidransom/liquidv1.9.1go.mod
All dependencies 43

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

RegistryPackageVersionRelation
Gogithub.com/alecthomas/chromav0.10.0direct
Gogithub.com/alecthomas/kingpin/v2v2.4.0direct
Gogithub.com/bep/godartsass/v2v2.5.0direct
Gogithub.com/bmatcuk/doublestar/v4v4.10.0direct
Gogithub.com/fsnotify/fsnotifyv1.9.0direct
Gogithub.com/gohugoio/hugo-goldmark-extensions/passthroughv0.3.1direct
Gogithub.com/google/go-githubv17.0.0+incompatibledirect
Gogithub.com/jaschaephraim/lrserverv0.0.0-20240306232639-afed386b3640direct
Gogithub.com/k0kubun/ppv3.0.1+incompatibledirect
Gogithub.com/kyokomi/emojiv2.2.4+incompatibledirect
Gogithub.com/montanaflynn/statsv0.7.1direct
Gogithub.com/pkg/browserv0.0.0-20240102092130-5ac0b6a4141cdirect
Gogithub.com/radovskyb/watcherv1.0.7direct
Gogithub.com/reidransom/liquidv1.9.1direct
Gogithub.com/stretchr/testifyv1.11.1direct
Gogithub.com/tdewolff/minifyv2.3.6+incompatibledirect
Gogithub.com/yuin/goldmarkv1.7.16direct
Gogithub.com/yuin/goldmark-highlightingv0.0.0-20220208100518-594be1970594direct
Gogolang.org/x/netv0.46.0direct
Gogolang.org/x/oauth2v0.30.0direct
Gogopkg.in/yaml.v2v2.4.0direct
RubyGemsjekyll-avatar—direct
RubyGemsjekyll-gist—direct
RubyGemsjekyll-github-metadata—direct
Gogithub.com/alecthomas/unitsv0.0.0-20240927000941-0f3dac36c52bindirect
Gogithub.com/davecgh/go-spewv1.1.1indirect
Gogithub.com/dlclark/regexp2v1.11.5indirect
Gogithub.com/google/go-querystringv1.1.0indirect
Gogithub.com/gorilla/websocketv1.5.3indirect
Gogithub.com/k0kubun/colorstringv0.0.0-20150214042306-9440f1994b88indirect
Gogithub.com/mattn/go-colorablev0.1.14indirect
Gogithub.com/mattn/go-isattyv0.0.20indirect
Gogithub.com/osteele/tuesdayv1.0.4indirect
Gogithub.com/pmezard/go-difflibv1.0.0indirect
Gogithub.com/tdewolff/parsev2.3.4+incompatibleindirect
Gogithub.com/tdewolff/testv1.0.11indirect
Gogithub.com/xhit/go-str2duration/v2v2.1.0indirect
Gogolang.org/x/modv0.29.0indirect
Gogolang.org/x/syncv0.18.0indirect
Gogolang.org/x/sysv0.37.0indirect
Gogolang.org/x/toolsv0.38.0indirect
Gogoogle.golang.org/protobufv1.36.8indirect
Gogopkg.in/yaml.v3v3.0.1indirect
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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with reidransom/gojekyll. Read them side by side →

98svix/svix-webhooksThe open source and enterprise-ready webhooks service 🦀Exceptional98ossf/osv-schemaOpen Source Vulnerability schema. Exceptional98buildkite/agentThe Buildkite Agent is an open-source toolkit written in Go for securely running build jobs on any device or networkExceptional100cilium/ciliumeBPF-based Networking, Security, and ObservabilityExceptional100hashicorp/consulConsul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.Exceptional100moby/mobyThe Moby Project - a collaborative project for the container ecosystem to assemble container-based systemsExceptional

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

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