Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 05:48 UTC

RemkoMolier / docker-hash

A tool to create a hash from a Dockerfile and its build arguments

GoMIT★ 0 stars⑂ 0 forkssince Apr 2026View on GitHub ↗
KindApplicationLibraryhow this is determined

RemkoMolier/docker-hash holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Security (83/100) and lowest on Community & Adoption (40/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Remko MolierPersonal account
0 followers21 public repossince Jan 2016

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/RemkoMolier/docker-hashv0.3.27-3541 days ago

Metrics by category

Vitality

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

67Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
0/36Commit cadence — 31/52 weeks with commits, discounted for automation: 0 of the last 100 commits human-authored, spanning 177 days
0/18Commit volume — 183 commits in the last year, discounted for automation: 0 of the last 100 commits human-authored, spanning 177 days
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_year183
human_commit_share0
days_since_last_push0
active_weeks_last_year31

Release discipline

98Exceptional
How it's scored
27/27Ships releases — 35 releases published
36/36Release recency — latest release 40 days ago
27/27Release cadence — a release every ~6.8 days
8/10OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count35
latest_release_tagv0.3.27
releases_from_tagsno
days_since_latest_release40
mean_days_between_releases6.8

Community & Adoption

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

40Weak · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgoreportcard.com, shields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

52Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
36.5/42Issue resolution — 87% of issues closed
29.4/30PR acceptance — 182/186 decided PRs merged
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_prs182
open_issues7
closed_issues47
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.87
closed_unmerged_prs4
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
0/25Owner reach — 0 followers of RemkoMolier
21.8/25Track record — 21 public repos, account ~10 yr old
Inputs used
followers0
owner_typeUser
is_verified—
owner_loginRemkoMolier
public_repos21
account_age_days3,972
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 41 days ago
20/20Version history — 35 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/RemkoMolier/docker-hash
ecosystemsgo
any_deprecatedno
min_days_since_publish41

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — .golangci.yml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

83Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 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 0/30 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is 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
5/5Pinned-Dependencies — all dependencies are pinned
4.5/5SAST — SAST tool detected but not run on all commits
5/5Security-Policy — security policy file detected
6/7.5Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
4.5/7.5Vulnerabilities — 4 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate7.9

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories4
affected_packages3
assessed_packages107
unassessed_packages0
affected_by_severityhigh 2, low 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 107 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.

57Moderate · 4% of overall
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.
How it's scored
12.6/18One-command bootstrap — go.mod (toolchain convention, no task runner)
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 agent-authored commits among the last 100
8/8Automated maintenance — 100 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, package-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share1
How it's scored
45/45Type-checkable code — Go (statically typed)
50.8/55Manageable file sizes — 1/13 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes79,419
source_files_sampled13
oversized_source_files1

Key facts

0GitHub stars
1contributors
183commits, last 12 months
0days since last push
35releases
1bus factor
7open issues
Gopackage ecosystems

More detail

OpenSSF Scorecard 7.9 / 10
7.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-11-18 05:48 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-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
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
6Vulnerabilities4 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
Gogithub.com/BurntSushi/tomlv1.6.0go.mod
Gogithub.com/google/go-containerregistryv0.22.1go.mod
Gogithub.com/moby/buildkitv0.35.0go.mod
Gogithub.com/moby/patternmatcherv0.6.1go.mod
All dependencies 107

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

RegistryPackageVersionRelation
Gogithub.com/burntsushi/tomlv1.6.0direct
Gogithub.com/google/go-containerregistryv0.22.1direct
Gogithub.com/moby/buildkitv0.35.0direct
Gogithub.com/moby/patternmatcherv0.6.1direct
Gogithub.com/containerd/typeurl/v2v2.3.0indirect
Gogithub.com/docker/cliv29.9.3+incompatibleindirect
Gogithub.com/docker/docker-credential-helpersv0.9.9indirect
Gogithub.com/klauspost/compressv1.20.2indirect
Gogithub.com/opencontainers/go-digestv1.0.0indirect
Gogithub.com/opencontainers/image-specv1.1.1indirect
Gogithub.com/pkg/errorsv0.9.1indirect
Gogithub.com/planetscale/vtprotobufv0.6.1-0.20240319094008-0393e58bdf10indirect
Gogithub.com/sirupsen/logrusv1.10.2indirect
Gogolang.org/x/syncv0.24.0indirect
Gogolang.org/x/sysv0.50.0indirect
Gogoogle.golang.org/protobufv1.36.12indirect
Gogotest.tools/v3v3.5.2indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@sindresorhus/merge-streams4.0.0indirect
npm@types/debug4.1.13indirect
npm@types/katex0.16.8indirect
npm@types/ms2.1.0indirect
npm@types/unist2.0.11indirect
npmansi-regex6.4.0indirect
npmargparse3.0.4indirect
npmbraces3.0.3indirect
npmcharacter-entities2.0.2indirect
npmcharacter-entities-legacy3.0.0indirect
npmcharacter-reference-invalid2.0.1indirect
npmcommander8.3.0indirect
npmdebug4.4.3indirect
npmdecode-named-character-reference1.3.0indirect
npmdequal2.0.3indirect
npmdevlop1.1.0indirect
npmentities8.1.0indirect
npmfast-glob3.3.3indirect
npmfastq1.20.1indirect
npmfill-range7.1.1indirect
npmget-east-asian-width1.7.0indirect
npmglob-parent5.1.2indirect
npmglobby16.2.4indirect
npmignore7.0.5indirect
npmis-alphabetical2.0.1indirect
npmis-alphanumerical2.0.1indirect
npmis-decimal2.0.1indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-hexadecimal2.0.1indirect
npmis-number7.0.0indirect
npmis-path-inside4.0.0indirect
npmjs-yaml5.5.0indirect
npmjsonc-parser3.3.1indirect
npmjsonpointer5.0.1indirect
npmkatex0.16.45indirect
npmlinkify-it6.1.0indirect
npmmarkdown-it15.0.3indirect
npmmarkdownlint0.42.1indirect
npmmarkdownlint-cli20.24.1indirect
npmmarkdownlint-cli2-formatter-default0.0.6indirect
npmmarkdownlint-rule-helpers0.18.0indirect
npmmarkdownlint-rule-max-one-sentence-per-line0.0.2indirect
npmmdurl2.1.0indirect
npmmerge21.4.1indirect
npmmicromark4.0.3indirect
npmmicromark-core-commonmark2.0.4indirect
npmmicromark-extension-directive4.0.0indirect
npmmicromark-extension-gfm-autolink-literal2.1.0indirect
npmmicromark-extension-gfm-footnote2.1.0indirect
npmmicromark-extension-gfm-table2.1.2indirect
npmmicromark-extension-math3.1.0indirect
npmmicromark-factory-destination2.0.1indirect
npmmicromark-factory-label2.0.1indirect
npmmicromark-factory-space2.1.0indirect
npmmicromark-factory-title2.0.1indirect
npmmicromark-factory-whitespace2.0.1indirect
npmmicromark-util-character2.1.1indirect
npmmicromark-util-chunked2.0.1indirect
npmmicromark-util-classify-character2.0.1indirect
npmmicromark-util-combine-extensions2.0.1indirect
npmmicromark-util-decode-numeric-character-reference2.0.2indirect
npmmicromark-util-edit-map1.0.0indirect
npmmicromark-util-encode2.0.1indirect
npmmicromark-util-html-tag-name2.0.1indirect
npmmicromark-util-normalize-identifier2.0.1indirect
npmmicromark-util-resolve-all2.0.1indirect
npmmicromark-util-sanitize-uri2.0.1indirect
npmmicromark-util-subtokenize2.1.0indirect
npmmicromark-util-symbol2.0.1indirect
npmmicromark-util-types2.0.3indirect
npmmicromatch4.0.8indirect
npmms2.1.3indirect
npmparse-entities4.0.2indirect
npmpicomatch2.3.2indirect
npmpunycode.js2.3.1indirect
npmqueue-microtask1.2.3indirect
npmre2js2.9.1indirect
npmreusify1.1.0indirect
npmrun-parallel1.2.0indirect
npmslash5.1.0indirect
npmsmol-toml1.6.1indirect
npmstring-width8.3.0indirect
npmstrip-ansi7.2.0indirect
npmto-regex-range5.0.1indirect
npmuc.micro3.0.0indirect
npmunicorn-magic0.4.0indirect
Dependency advisories 3

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

PackageVersionRelationSeverityAdvisoriesFixed in
picomatch2.3.2indirecthigh1—
smol-toml1.6.1indirecthigh21.9.0
katex0.16.45indirectlow10.18.2

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 — Go.