Public record
Software health reportschema 0.27.0 · metrics 2.5.0 · 2026-07-27 15:43 UTC

beenotung / quick-erd

quick and easy text-based ERD editor with drag and drop visualization + code generator for migration, query, typescript types and orm entity

TypeScriptBSD-2-Clause★ 62 stars⑂ 6 forkssince Aug 2021View on GitHub ↗

beenotung/quick-erd holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Vitality (74/100) and lowest on Security (40/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Beeno TungPersonal account
176 followers624 public repossince Nov 2013

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
npmquick-erd4.35.02,1561766 days agoerddiagramofflinelocal-first

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
4.2/36Commit cadence — 6/52 weeks with commits
16/18Commit volume — 60 commits in the last year
9/10OpenSSF Scorecard: Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year60
human_commit_share1
days_since_last_push3
active_weeks_last_year6
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 6 days ago
27/27Release cadence — a release every ~34.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv4.35.0
releases_from_tagsyes
days_since_latest_release6
mean_days_between_releases34.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?

46Weak · 17% of overall
How it's scored
29/60Stars — 62 stars
5.8/25Forks — 6 forks
1.7/15Watchers — 3 watchers
Inputs used
forks6
stars62
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-2-Clause)
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
How it's scored
44.5/80Monthly downloads — 2,156 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesquick-erd
dependents
ecosystemsnpm
total_downloads
monthly_downloads2,156
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?

48Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
31.5/42Issue resolution — 75% of issues closed
0/30PR acceptance — 0/1 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues1
closed_issues3
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.75
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
16.2/25Owner reach — 176 followers of beenotung
25/25Track record — 624 public repos, account ~12 yr old
Inputs used
followers176
owner_typeUser
is_verified
owner_loginbeenotung
public_repos624
account_age_days4,630
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 6 days ago
20/20Version history — 176 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesquick-erd
ecosystemsnpm
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — .eslintrc
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigyes
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 site — https://erd.surge.sh
10/10Repository description
10/10Topics — 3 topics
10/10Wiki
Inputs used
topicserd, text-based, drag-and-drop
has_wikiyes
homepagehttps://erd.surge.sh
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

40Weak · 16% of overall
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/30 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
6.8/7.5Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 69 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate2.5
Excluded from scoring (no data or not applicable): ci_tests, dangerous_workflow, packaging, pinned_dependencies, signed_releases, token_permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages218
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:quick-erd@4.35.0 runtime dependency closure — what installing the published package pulls in — 218 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.

58Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 76 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.76
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrap — examples/java-project/pom.xml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — .eslintrc
11/11Static type checking — examples/node-project/tsconfig.json, tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsexamples/node-project/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifestsexamples/java-project/pom.xml
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/91 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes35,076
source_files_sampled91
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — example, examples
Inputs used
example_dirsexample, examples
has_mcp_signalno
api_schema_files

Key facts

62GitHub stars
1contributors
60commits, last 12 months
3days since last push
100releases
1bus factor
1open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 6 ⇿
0Stars
6Forks
92Releases

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.

123456612023-012024-062025-11
Major 0Minor 27Patch 65

Each point covers 3 days.

OpenSSF Scorecard 2.5 / 10
2.5aggregate

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-27 15:43 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
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
9Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities69 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmfastest-levenshtein^1.0.16package.json
npmopen^11.0.0package.json
All dependencies 48

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

RegistryPackageVersionRelation
npmfastest-levenshtein^1.0.16direct
npmopen^11.0.0direct
Mavencom.h2database:h22.2.224indirect
Mavenorg.springframework.boot:spring-boot-maven-pluginindirect
Mavenorg.springframework.boot:spring-boot-starter-data-jpaindirect
Mavenorg.springframework.boot:spring-boot-starter-testindirect
Mavenorg.springframework.boot:spring-boot-starter-webindirect
npm@types/better-sqlite3^7.6.13indirect
npm@types/chai^4.3.20indirect
npm@types/express^4.17.25indirect
npm@types/integer^4.0.3indirect
npm@types/mocha^10.0.10indirect
npm@types/node^24.13.3indirect
npmbetter-sqlite3^12.11.1indirect
npmbetter-sqlite3^12.4.1indirect
npmbetter-sqlite3-proxy^2.11.4indirect
npmbetter-sqlite3-schema^3.1.10indirect
npmchai^4.5.0indirect
npmdotenv^17.2.3indirect
npmdotenv^17.4.2indirect
npmesbuild^0.25.12indirect
npmexpress^4.22.2indirect
npmformat-json-cli^1.1.0indirect
npmgen-env^1.0.1indirect
npmknex^2 || ^3indirect
npmknex^3.3.0indirect
npmlistening-on^2.1.0indirect
npmmocha^11.7.6indirect
npmmysql^2.18.1indirect
npmnpm-run-all^4.1.5indirect
npmnyc^17.1.0indirect
npmoklab.ts^2.2.7indirect
npmopen-cli^8.0.0indirect
npmpg^8.16.3indirect
npmpg^8.22.0indirect
npmpopulate-env^2.6.1indirect
npmprettier^3.9.5indirect
npmpsql-shell^1.4.0indirect
npmrimraf^6.1.3indirect
npmsass^1.101.0indirect
npmserve-lite^1.6.2indirect
npmsurge^0.33.0indirect
npmtedious^16.7.1indirect
npmtedious^18.6.1indirect
npmts-mocha^11.1.0indirect
npmts-node^10.9.2indirect
npmts-node-dev^2.0.0indirect
npmtypescript^6.0.3indirect
Dependency advisories 0

Installing npm:quick-erd@4.35.0 pulls in 218 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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

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

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