Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-31 21:53 UTC

dimm-city / gutterpress

TypeScript · SvelteCustom license★ 0 stars⑂ 0 forkssince Jan 2026View on GitHub ↗

dimm-city/gutterpress holds a health index of 67 out of 100, placing it in the Good band. It scores highest on AI Readiness (81/100) and lowest on Community & Adoption (32/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Dimm City RPGOrganization
1 follower6 public repossince Oct 2021

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmgutterpress0.0.012222 days agomarkdownpdfprintpagedjsghostscriptbookpublishingttrpg

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
4.8/36Commit cadence7/52 weeks with commits
18/18Commit volume510 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year510
human_commit_share0.98
days_since_last_push0
active_weeks_last_year7
How it's scored
27/27Ships releases27 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~3.1 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count27
latest_release_tagv0.9.0-alpha.1
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases3.1

Community & Adoption

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

32At Risk · 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
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
27.9/80Monthly downloads122 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesgutterpress
dependents
ecosystemsnpm
total_downloads
monthly_downloads122
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

63Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.1/22.5Commit distributiontop contributor authored 55% of commits
4.1/13.5Contributor breadth3 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.549
How it's scored
40.5/42Issue resolution96% of issues closed
29.6/30PR acceptance76/77 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 1/4 approved changesets -- score normalized to 2
Inputs used
merged_prs76
open_issues2
closed_issues55
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.965
closed_unmerged_prs1
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
2.2/25Owner reach1 followers of dimm-city
15.7/25Track record6 public repos, account ~4 yr old
Inputs used
followers1
owner_typeOrganization
is_verified
owner_logindimm-city
public_repos6
account_age_days1,742
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 2 days ago
12/20Version history2 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgutterpress
ecosystemsnpm
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

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

51Moderate · 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
2.5/2.5CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 1/4 approved changesets -- score normalized to 2
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
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-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.2
How it's scored
20.2/35Direct dependencies free of known advisories1 affected: tar 7.5.20 (moderate 5.3)
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
40/40No advisories left outstandingno advisory has been public longer than 90 days
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages192
unassessed_packages0
affected_by_severitymoderate 1
direct_affected_packages1
Matched the npm:gutterpress@0.0.0 runtime dependency closure — what installing the published package pulls in — 192 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.

81Excellent · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history83 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.847
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes25,540
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.js
11/11Static type checking.svelte-kit/tsconfig.json, packages/cli/tsconfig.json, packages/desktop/electron/tsconfig.json, packages/desktop/tsconfig.json
10/10Reproducible environmentDockerfile
10/10Demonstrated agent practice70 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs.svelte-kit/tsconfig.json, packages/cli/tsconfig.json, packages/desktop/electron/tsconfig.json, packages/desktop/tsconfig.json
agent_commit_share0.7
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.8/55Manageable file sizes3/743 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes94,199
source_files_sampled743
oversized_source_files3
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
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
3contributors
510commits, last 12 months
0days since last push
27releases
1bus factor
2open issues
npmpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-31 21:53 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 1/4 approved changesets -- score normalized to 2
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 9 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
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
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 41
RegistryPackageVersion constraintManifest
npmacorn8.16.0packages/cli/package.json
npmchokidar^5.0.0packages/cli/package.json
npmcitty^0.2.0packages/cli/package.json
npmdiff30.0.3packages/cli/package.json
npmes-module-lexer2.0.0packages/cli/package.json
npmfflate0.8.3packages/cli/package.json
npmglob^13.0.0packages/cli/package.json
npmhtmlhint^1.9.2packages/cli/package.json
npmisomorphic-git^1.38.4packages/cli/package.json
npmmarkdown-it^14.1.0packages/cli/package.json
npmmarkdown-it-abbr^2.0.0packages/cli/package.json
npmmarkdown-it-attrs^4.3.0packages/cli/package.json
npmmarkdown-it-deflist^3.0.1packages/cli/package.json
npmmarkdown-it-footnote^4.0.0packages/cli/package.json
npmmarkdown-it-mark^4.0.0packages/cli/package.json
npmmarkdown-it-source-map^0.1.1packages/cli/package.json
npmmarkdown-it-sub^2.0.0packages/cli/package.json
npmmarkdown-it-sup^2.0.0packages/cli/package.json
npmmarkdownlint^0.40.0packages/cli/package.json
npmpdf-lib^1.17.1packages/cli/package.json
npmpostcss^8.5.18packages/cli/package.json
npmpuppeteer-core^25.0.4packages/cli/package.json
npmresolve.exports2.0.3packages/cli/package.json
npmsemver7.8.0packages/cli/package.json
npmtar7.5.20packages/cli/package.json
npmunpdf^1.6.2packages/cli/package.json
npmws^8.21.0packages/cli/package.json
npmyaml^2.8.2packages/cli/package.json
npm@codemirror/autocomplete^6.18.4packages/desktop/package.json
npm@codemirror/commands^6.8.0packages/desktop/package.json
npm@codemirror/lang-css^6.3.1packages/desktop/package.json
npm@codemirror/lang-markdown^6.3.1packages/desktop/package.json
npm@codemirror/language^6.10.8packages/desktop/package.json
npm@codemirror/language-data^6.5.1packages/desktop/package.json
npm@codemirror/lint^6.8.4packages/desktop/package.json
npm@codemirror/state^6.5.2packages/desktop/package.json
npm@codemirror/view^6.36.2packages/desktop/package.json
npmgutterpressworkspace:*packages/desktop/package.json
npm@lezer/highlight^1.2.3packages/desktop/package.json
npmelectron-updater^6.6.2packages/desktop/package.json
npmsemver~7.7.3packages/desktop/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

Dependency advisories 1

Installing npm:gutterpress@0.0.0 pulls in 192 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
tar7.5.20directmoderate17.5.21

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

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