Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-04 10:52 UTC

oidoid / mem

🤖 Proportional and monospaced sans light pixel font family.

HTMLAGPL-3.0★ 80 stars⑂ 1 forksince Nov 2016View on GitHub ↗

oidoid/mem holds a health index of 47 out of 100, placing it in the Weak band. It scores highest on Engineering Quality (56/100) and lowest on AI Readiness (40/100). It was last updated 11 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

oidoidOrganization · verified domain
4 followers19 public repossince Feb 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmmem-font11.0.0-132,6023736 days agofontttfpixelmonospacedfixed-widthproportional8-bitretrofontforgeasepritegameminimalsans

Metrics by category

Vitality

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

53Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 11 days ago
5.5/36Commit cadence8/52 weeks with commits
13.4/18Commit volume30 commits in the last year
1/10OpenSSF Scorecard: Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year30
human_commit_share1
days_since_last_push11
active_weeks_last_year8
How it's scored
16.2/27Ships releases45 version tags (no GitHub releases)
16.2/36Release recencylatest release 245 days ago
19.8/27Release cadencea release every ~72.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count45
latest_release_tagv11.0.0-10
releases_from_tagsyes
days_since_latest_release245
mean_days_between_releases72.2
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?

44Weak · 17% of overall
How it's scored
30.8/60Stars80 stars
0/25Forks1 forks
0/15Watchers1 watchers
Inputs used
forks1
stars80
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (AGPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
45.5/80Monthly downloads2,602 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmem-font
dependents
ecosystemsnpm
total_downloads
monthly_downloads2,602
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?

43Weak · 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
0/42Issue resolutionno issues or no data
0/30PR acceptanceno decided pull requests or no data
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_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
5/25Owner reach4 followers of oidoid
20.6/25Track record19 public repos, account ~5 yr old
Inputs used
followers4
owner_typeOrganization
is_verifiedyes
owner_loginoidoid
public_repos19
account_age_days2,040

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 36 days ago
20/20Version history37 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmem-font
ecosystemsnpm
any_deprecatedno
min_days_since_publish36

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno 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.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://rndmem.com
10/10Repository description
10/10Topics13 topics
0/10Wiki
Inputs used
topicsfont, ttf, pixel, fixed-width, proportional, 8-bit, retro, fontforge, aseprite, game, minimal, sans, monospaced
has_wikino
homepagehttps://rndmem.com
docs_sitehttps://rndmem.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

47Weak · 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/2.5CI-Testsno data
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
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0.8/7.5Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5Packagingno data
1.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages38
unassessed_packages0
affected_by_severitynone
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 38 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.

40Weak · 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 history0 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstraptools/makefile
0/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
3/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_filestools/makefile
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codeHTML with type-check config (tsconfig.json)
55/55Manageable file sizes0/1 source files over 60KB
Inputs used
primary_languageHTML
largest_source_bytes2,787
source_files_sampled1
oversized_source_files0

Key facts

80GitHub stars
1contributors
30commits, last 12 months
11days since last push
45releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 3.4 / 10
3.4aggregate

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-04 10:52 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/30 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
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 38

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

RegistryPackageVersionRelation
npm@biomejs/biome2.3.10indirect
npm@biomejs/cli-darwin-arm642.3.10indirect
npm@biomejs/cli-darwin-x642.3.10indirect
npm@biomejs/cli-linux-arm642.3.10indirect
npm@biomejs/cli-linux-arm64-musl2.3.10indirect
npm@biomejs/cli-linux-x642.3.10indirect
npm@biomejs/cli-linux-x64-musl2.3.10indirect
npm@biomejs/cli-win32-arm642.3.10indirect
npm@biomejs/cli-win32-x642.3.10indirect
npm@esbuild/aix-ppc640.27.2indirect
npm@esbuild/android-arm0.27.2indirect
npm@esbuild/android-arm640.27.2indirect
npm@esbuild/android-x640.27.2indirect
npm@esbuild/darwin-arm640.27.2indirect
npm@esbuild/darwin-x640.27.2indirect
npm@esbuild/freebsd-arm640.27.2indirect
npm@esbuild/freebsd-x640.27.2indirect
npm@esbuild/linux-arm0.27.2indirect
npm@esbuild/linux-arm640.27.2indirect
npm@esbuild/linux-ia320.27.2indirect
npm@esbuild/linux-loong640.27.2indirect
npm@esbuild/linux-mips64el0.27.2indirect
npm@esbuild/linux-ppc640.27.2indirect
npm@esbuild/linux-riscv640.27.2indirect
npm@esbuild/linux-s390x0.27.2indirect
npm@esbuild/linux-x640.27.2indirect
npm@esbuild/netbsd-arm640.27.2indirect
npm@esbuild/netbsd-x640.27.2indirect
npm@esbuild/openbsd-arm640.27.2indirect
npm@esbuild/openbsd-x640.27.2indirect
npm@esbuild/openharmony-arm640.27.2indirect
npm@esbuild/sunos-x640.27.2indirect
npm@esbuild/win32-arm640.27.2indirect
npm@esbuild/win32-ia320.27.2indirect
npm@esbuild/win32-x640.27.2indirect
npm@oidoid/config0.0.3indirect
npmesbuild0.27.2indirect
npmtypescript5.9.3indirect
Dependency advisories 0

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

No known advisories affect the assessed dependencies.

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