Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 08:24 UTC

michael-duren / rubber-duck

Go · templ · CNo license detected★ 0 stars⑂ 0 forkssince Jul 2026View on GitHub ↗
KindApplicationLibraryhow this is determined

michael-duren/rubber-duck holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on AI Readiness (83/100) and lowest on Community & Adoption (12/100). It was last updated 39 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Michael DurenPersonal account
37 followers125 public repossince Mar 2022Target

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
Gogithub.com/michael-duren/rubber-duckv0.2.1-1553 days ago
npmrubber-duckpoints to another repo — not scored1.0.02024372 days agodebuggingrubberduckquack

Metrics by category

Vitality

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

59Moderate · 21% of overall
How it's scored
18/36Push recencylast push 39 days ago
2.8/36Commit cadence4/52 weeks with commits
18/18Commit volume107 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year107
human_commit_share1
days_since_last_push39
active_weeks_last_year4
How it's scored
27/27Ships releases15 releases published
36/36Release recencylatest release 53 days ago
27/27Release cadencea release every ~1.3 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count15
latest_release_tagv0.2.1
releases_from_tagsno
days_since_latest_release53
mean_days_between_releases1.3

Community & Adoption

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

12Critical · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
34.2/42Issue resolution82% of issues closed
29.6/30PR acceptance67/68 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_prs67
open_issues5
closed_issues22
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.815
closed_unmerged_prs1
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
11.4/25Owner reach37 followers of michael-duren
22.1/25Track record125 public repos, account ~4 yr old
Inputs used
followers37
owner_typeUser
is_verified
owner_loginmichael-duren
public_repos125
account_age_days1,654
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 go
35/35Publish recencylatest publish 53 days ago
20/20Version history15 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/michael-duren/rubber-duck
ecosystemsgo
any_deprecatedno
min_days_since_publish53

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests25 out of 26 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

36Weak · 16% of overall
How it's scored
0/7.5Binary-Artifactsbinaries present in source code
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.2/2.5CI-Tests25 out of 26 merged PRs checked by a CI test -- score normalized to 9
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
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
5/5Packagingpackaging workflow detected
2.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities18 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate3
How it's scored
8/35Direct dependencies free of known advisories2 affected: lodash 2.4.1 (critical 9.1), string 2.0.1 (high 7.5)
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
28.3/40No advisories left outstanding2 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,969 days ago
Inputs used
sourceosv
advisories6
affected_packages2
assessed_packages9
unassessed_packages0
affected_by_severitycritical 1, high 1
direct_affected_packages2
Matched the npm:rubber-duck@1.0.0 runtime dependency closure — what installing the published package pulls in — 9 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.

83Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history97 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.97
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes7,077
How it's scored
18/18One-command bootstrapMakefile, courses/os/boot/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingvscode-extension/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice19 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
5/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, package-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile, courses/os/boot/Makefile
has_devcontainerno
has_linter_configno
typecheck_configsvscode-extension/tsconfig.json
agent_commit_share0.19
toolchain_manifestsgo.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeGo (statically typed)
54.7/55Manageable file sizes1/173 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes919,083
source_files_sampled173
oversized_source_files1

Key facts

0GitHub stars
1contributors
107commits, last 12 months
39days since last push
15releases
1bus factor
5open issues
Go, npmpackage ecosystems

Data collection warnings

  • npm package 'rubber-duck' points at a different repository (https://github.com/tleen/rubber-duck); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.0 / 10
3.0aggregate

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-10 08:24 UTC

0Binary-Artifactsbinaries present in source code
5Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests25 out of 26 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
10Packagingpackaging workflow detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0SASTSAST tool is not run on all commits -- score normalized to 0
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
0Vulnerabilities18 existing vulnerabilities detected
Direct dependencies 26
RegistryPackageVersion constraintManifest
npm@codemirror/commands^6.7.1editor/package.json
npm@codemirror/lang-cpp^6.0.2editor/package.json
npm@codemirror/lang-go^6.0.1editor/package.json
npm@codemirror/lang-javascript^6.2.2editor/package.json
npm@codemirror/lang-markdown^6.5.1editor/package.json
npm@codemirror/lang-python^6.1.6editor/package.json
npm@codemirror/language^6.10.8editor/package.json
npm@codemirror/state^6.5.0editor/package.json
npm@codemirror/theme-one-dark^6.1.2editor/package.json
npm@codemirror/view^6.36.1editor/package.json
npm@replit/codemirror-vim^6.2.1editor/package.json
npmcodemirror^6.0.1editor/package.json
Gocloud.google.com/go/runv1.21.0go.mod
Gocloud.google.com/go/storagev1.63.0go.mod
Gogithub.com/a-h/templv0.3.1020go.mod
Gogithub.com/alecthomas/chroma/v2v2.27.0go.mod
Gogithub.com/golang-migrate/migrate/v4v4.19.1go.mod
Gogithub.com/jackc/pgx/v5v5.10.0go.mod
Gogithub.com/yuin/goldmarkv1.8.2go.mod
Gogithub.com/yuin/goldmark-highlighting/v2v2.0.0-20230729083705-37449abec8ccgo.mod
Gogo.abhg.dev/goldmark/frontmatterv0.3.0go.mod
Gogolang.org/x/cryptov0.53.0go.mod
Gogolang.org/x/termv0.44.0go.mod
Gogoogle.golang.org/protobufv1.36.11go.mod
Gooss.terrastruct.com/d2v0.7.1go.mod
Gooss.terrastruct.com/util-gov0.0.0-20250213174338-243d8661088ago.mod
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 2

Installing npm:rubber-duck@1.0.0 pulls in 9 packages, direct and transitive: 2 carry known advisories, of which 2 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
lodash2.4.1directcritical54.18.0
string2.0.1directhigh1

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 statisticsGo, npm.