Public record
Software health reportschema 0.17.0 · metrics 2.10.0 · 2026-07-21 05:36 UTC

songtianlun / diarum

Diarum - A simple, elegant, and self-hosted diary application. 一个简洁、优雅、可自托管的日记应用。

Go · Svelte · TypeScriptApache-2.0★ 158 stars⑂ 17 forkssince Jan 2026View on GitHub ↗
KindNetwork servicehow this is determined

songtianlun/diarum holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (82/100) and lowest on Security (33/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

63
overall / 100
Moderate

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.

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

Ownership

TianLun SongPersonal account
66 followers63 public repossince Sep 2017

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/songtianlun/diarumv0.8.3-356 days ago

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
9/36Commit cadence13/52 weeks with commits
17.4/18Commit volume86 commits in the last year
8/10OpenSSF Scorecard: Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year86
human_commit_share
days_since_last_push4
active_weeks_last_year13

Release discipline

100Exceptional
How it's scored
27/27Ships releases33 releases published
36/36Release recencylatest release 6 days ago
27/27Release cadencea release every ~14.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count33
latest_release_tagv0.8.3
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases14.6
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?

48Weak · 17% of overall
How it's scored
35.6/60Stars158 stars
10/25Forks17 forks
0/15Watchers1 watchers
Inputs used
forks17
stars158
watchers1
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.3/22.5Commit distributiontop contributor authored 99% of commits
2.7/13.5Contributor breadth2 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.988
How it's scored
34.3/42Issue resolution82% of issues closed
27.2/30PR acceptance49/54 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/29 approved changesets -- score normalized to 0
Inputs used
merged_prs49
open_issues7
closed_issues31
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.816
closed_unmerged_prs5
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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
13.1/25Owner reach66 followers of songtianlun
25/25Track record63 public repos, account ~8 yr old
Inputs used
followers66
owner_typeUser
is_verified
owner_loginsongtianlun
public_repos63
account_age_days3,232
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 6 days ago
20/20Version history35 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/songtianlun/diarum
ecosystemsgo
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests9 out of 24 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://demo.diarum.app
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicsjournal, self-hosted
has_wikino
homepagehttps://demo.diarum.app
docs_sitehttps://demo.diarum.app
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

33At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0.8/2.5CI-Tests9 out of 24 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/29 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
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
6/7.5Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities30 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.3
Excluded from scoring (no data or not applicable): Signed-Releases. 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.

53Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno 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
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingsite/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configssite/tsconfig.json
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.
How it's scored
45/45Type-checkable codeGo (statically typed)
54.2/55Manageable file sizes1/65 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes78,499
source_files_sampled65
oversized_source_files1

Key facts

158GitHub stars
2contributors
86commits, last 12 months
4days since last push
33releases
1bus factor
7open issues
Go, npmpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 158 ★ / 0 ⇿
158Stars

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.

04080120160158312026-012026-042026-07
OpenSSF Scorecard 3.3 / 10
3.3aggregate

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-21 05:36 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
3CI-Tests9 out of 24 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/29 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities30 existing vulnerabilities detected
Direct dependencies 29
RegistryPackageVersion constraintManifest
Gogithub.com/aws/aws-sdk-go-v2v1.36.3go.mod
Gogithub.com/aws/aws-sdk-go-v2/configv1.29.12go.mod
Gogithub.com/aws/aws-sdk-go-v2/credentialsv1.17.65go.mod
Gogithub.com/aws/aws-sdk-go-v2/service/s3v1.60.1go.mod
Gogithub.com/golang-jwt/jwt/v5v5.2.1go.mod
Gogithub.com/labstack/echo/v5v5.0.0-20230722203903-ec5b858dab61go.mod
Gogithub.com/philippgille/chromem-gov0.7.0go.mod
Gogolang.org/x/cryptov0.36.0go.mod
Gomodernc.org/sqlitev1.36.1go.mod
npm@tiptap/core^2.11.5site/package.json
npm@tiptap/extension-bubble-menu^2.11.5site/package.json
npm@tiptap/extension-character-count^2.11.5site/package.json
npm@tiptap/extension-code-block-lowlight^2.11.5site/package.json
npm@tiptap/extension-dropcursor^2.11.5site/package.json
npm@tiptap/extension-focus^2.27.2site/package.json
npm@tiptap/extension-highlight^2.11.5site/package.json
npm@tiptap/extension-image^2.11.5site/package.json
npm@tiptap/extension-link^2.11.5site/package.json
npm@tiptap/extension-placeholder^2.11.5site/package.json
npm@tiptap/extension-task-item^2.11.5site/package.json
npm@tiptap/extension-task-list^2.11.5site/package.json
npm@tiptap/extension-typography^2.11.5site/package.json
npm@tiptap/extension-underline^2.11.5site/package.json
npm@tiptap/pm^2.11.5site/package.json
npm@tiptap/starter-kit^2.11.5site/package.json
npm@tiptap/suggestion^2.11.5site/package.json
npmhtml-to-image^1.11.13site/package.json
npmlowlight^3.2.0site/package.json
npmmarked^17.0.1site/package.json
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

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

How one result sits in the wider record: aggregate statisticsGo.