Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 21:12 UTC

utking / code-snippets

A small GoLang Web app for managing code snippets. Uses SQLite as a storage

Go · Vue · HTMLNo license detected★ 0 stars⑂ 0 forkssince Aug 2022archivedView on GitHub ↗
KindNetwork serviceWeb interfacehow this is determined

utking/code-snippets holds a health index of 9 out of 100, placing it in the Critical band. It scores highest on Engineering Quality (50/100) and lowest on Community & Adoption (12/100). The repository is archived, so no further maintenance is expected.

9
overall / 100
Critical

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.

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

Ownership

Gennady UtkinPersonal account
8 followers20 public repossince Jun 2010OpticsPlanet

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/utking/code-snippetsv0.9.92-41354 days ago

Metrics by category

Vitality

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

19Critical · 21% of overall

Development activity

1Critical
How it's scored
0/36Push recency — last push 1,354 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — project is archived
Inputs used
commits_last_year0
human_commit_share—
days_since_last_push1,354
active_weeks_last_year0

Release discipline

47Weak
How it's scored
27/27Ships releases — 2 releases published
0/36Release recency — latest release 1,354 days ago
19.8/27Release cadence — a release every ~71.9 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count2
latest_release_tagv0.9.92
releases_from_tagsno
days_since_latest_release1,354
mean_days_between_releases71.9

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 — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

25At Risk
How it's scored
22.5/22.5README
0/22.5License — no 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_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?

35Weak · 23% of overall

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/27 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

48Weak
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
6.9/25Owner reach — 8 followers of utking
21.6/25Track record — 20 public repos, account ~16 yr old
Inputs used
followers8
owner_typeUser
is_verified—
owner_loginutking
public_repos20
account_age_days5,867
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

61Moderate
How it's scored
25/25Published & resolvable — 1 package(s) on go
4/35Publish recency — latest publish 1,354 days ago
12/20Version history — 4 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/utking/code-snippets
ecosystemsgo
any_deprecatedno
min_days_since_publish1,354

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 19% of overall

Engineering practices

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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
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?

18Critical · 16% of overall

Security posture

18Critical
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
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/27 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
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
0/7.5Maintained — project is archived
0/5Packaging — no data
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/7.5Vulnerabilities — 97 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate1.8
Excluded from scoring (no data or not applicable): CI-Tests, Packaging. 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.

36Weak · 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)

39Weak
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — .golangci.yaml
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — 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_testsno
lockfilesgo.sum, package-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
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

96Exceptional
How it's scored
45/45Type-checkable code — Go (statically typed)
51.1/55Manageable file sizes — 1/14 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes1,120,321
source_files_sampled14
oversized_source_files1

Key facts

0GitHub stars
-contributors
0commits, last 12 months
1,354days since last push
2releases
-bus factor
0open issues
Go, npmpackage ecosystems

Data collection warnings

  • Contributor list unavailable

More detail

OpenSSF Scorecard 1.8 / 10
1.8aggregate

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-17 21:12 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/27 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintainedproject is archived
n/aPackagingpackaging workflow not 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
0Vulnerabilities97 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
Gogithub.com/dannyvankooten/extemplatev0.0.0-20210615115643-8f1c15f70e70backend/go.mod
Gogithub.com/google/uuidv1.3.0backend/go.mod
Gogithub.com/gorilla/sessionsv1.2.1backend/go.mod
Gogithub.com/labstack/echo/v4v4.9.0backend/go.mod
Gogithub.com/mattn/go-sqlite3v1.14.16backend/go.mod
Gogolang.org/x/cryptov0.0.0-20210817164053-32db794688a5backend/go.mod
Goxorm.io/xormv1.3.2backend/go.mod
npmaxios^0.27.2package.json
npmvue^3.2.37package.json
npmvue-axios^3.4.1package.json
npmvue-router^4.1.3package.json
npmvue3-highlightjs^1.0.5package.json
All dependencies 66

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

RegistryPackageVersionRelation
npmaxios0.27.2direct
npmvue3.2.37direct
npmvue-axios3.4.1direct
npmvue-router4.1.3direct
npmvue3-highlightjs1.0.5direct
npm@babel/parser7.18.11indirect
npm@esbuild/linux-loong640.14.53indirect
npm@vitejs/plugin-vue3.0.1indirect
npm@vue/compiler-core3.2.37indirect
npm@vue/compiler-dom3.2.37indirect
npm@vue/compiler-sfc3.2.37indirect
npm@vue/compiler-ssr3.2.37indirect
npm@vue/devtools-api6.2.1indirect
npm@vue/reactivity3.2.37indirect
npm@vue/reactivity-transform3.2.37indirect
npm@vue/runtime-core3.2.37indirect
npm@vue/runtime-dom3.2.37indirect
npm@vue/server-renderer3.2.37indirect
npm@vue/shared3.2.37indirect
npmasynckit0.4.0indirect
npmcombined-stream1.0.8indirect
npmcsstype2.6.20indirect
npmdelayed-stream1.0.0indirect
npmesbuild0.14.53indirect
npmesbuild-android-640.14.53indirect
npmesbuild-android-arm640.14.53indirect
npmesbuild-darwin-640.14.53indirect
npmesbuild-darwin-arm640.14.53indirect
npmesbuild-freebsd-640.14.53indirect
npmesbuild-freebsd-arm640.14.53indirect
npmesbuild-linux-320.14.53indirect
npmesbuild-linux-640.14.53indirect
npmesbuild-linux-arm0.14.53indirect
npmesbuild-linux-arm640.14.53indirect
npmesbuild-linux-mips64le0.14.53indirect
npmesbuild-linux-ppc64le0.14.53indirect
npmesbuild-linux-riscv640.14.53indirect
npmesbuild-linux-s390x0.14.53indirect
npmesbuild-netbsd-640.14.53indirect
npmesbuild-openbsd-640.14.53indirect
npmesbuild-sunos-640.14.53indirect
npmesbuild-windows-320.14.53indirect
npmesbuild-windows-640.14.53indirect
npmesbuild-windows-arm640.14.53indirect
npmestree-walker2.0.2indirect
npmfollow-redirects1.15.1indirect
npmform-data4.0.0indirect
npmfsevents2.3.2indirect
npmfunction-bind1.1.1indirect
npmhas1.0.3indirect
npmhighlight.js10.7.3indirect
npmis-core-module2.10.0indirect
npmmagic-string0.25.9indirect
npmmime-db1.52.0indirect
npmmime-types2.1.35indirect
npmnanoid3.3.4indirect
npmpath-parse1.0.7indirect
npmpicocolors1.0.0indirect
npmpostcss8.4.16indirect
npmresolve1.22.1indirect
npmrollup2.77.2indirect
npmsource-map0.6.1indirect
npmsource-map-js1.0.2indirect
npmsourcemap-codec1.4.8indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmvite3.0.4indirect
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 utking/code-snippets. Read them side by side →

100apache/airflowApache Airflow - A platform to programmatically author, schedule, and monitor workflowsExceptional100mattermost/mattermostMattermost is an open source platform for secure collaboration across the entire software development lifecycle..Exceptional100coder/coderSecure environments for developers and their agentsExceptional100hashicorp/consulConsul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.Exceptional99go-gitea/giteaGit with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CDExceptional99kubernetes-sigs/kueueKubernetes-native Job QueueingExceptional

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

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