Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 16:00 UTC

cyjake / leoric

👑 JavaScript ORM for MySQL, PostgreSQL, and SQLite.

JavaScript · TypeScriptBSD-3-Clause★ 234 stars⑂ 20 forkssince Dec 2017View on GitHub ↗

cyjake/leoric holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (86/100) and lowest on Community & Adoption (63/100). It was last updated 31 days ago. A single contributor accounts for most of its recent work.

86
overall / 100
Excellent

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.

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

Ownership

Chen YangjianPersonal account
422 followers64 public repossince Apr 2010Alibaba Group

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
npmleoric2.16.08,46716131 days agomodelmysqlormpostgresqlquery-buildersqlite

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
18/36Push recencylast push 31 days ago
10.4/36Commit cadence15/52 weeks with commits
15.9/18Commit volume58 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year58
human_commit_share0.95
days_since_last_push31
active_weeks_last_year15

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 31 days ago
27/27Release cadencea release every ~18.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv2.16.0
releases_from_tagsno
days_since_latest_release31
mean_days_between_releases18.3
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?

63Moderate · 17% of overall
How it's scored
38.4/60Stars234 stars
10.7/25Forks20 forks
5.8/15Watchers12 watchers
Inputs used
forks20
stars234
watchers12
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (BSD-3-Clause)
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
52.4/80Monthly downloads8,467 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesleoric
dependents
ecosystemsnpm
total_downloads
monthly_downloads8,467
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?

73Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.8/22.5Commit distributiontop contributor authored 65% of commits
13.5/13.5Contributor breadth23 contributors
10/10OpenSSF Scorecard: Contributorsproject has 34 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled23
top_contributor_share0.653
How it's scored
41.5/42Issue resolution99% of issues closed
28.6/30PR acceptance395/415 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs395
open_issues1
closed_issues89
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.989
closed_unmerged_prs20
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
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
18.9/25Owner reach422 followers of cyjake
25/25Track record64 public repos, account ~16 yr old
Inputs used
followers422
owner_typeUser
is_verified
owner_logincyjake
public_repos64
account_age_days5,989
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 npm
35/35Publish recencylatest publish 31 days ago
20/20Version history161 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesleoric
ecosystemsnpm
any_deprecatedno
min_days_since_publish31

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config.eslintrc, .eslintrc.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://leoric.js.org
10/10Repository description
10/10Topics6 topics
0/10Wiki
Inputs used
topicsnodejs, nodejs-modules, mysql, orm, postgresql, querybuilder
has_wikino
homepagehttps://leoric.js.org
docs_sitehttps://leoric.js.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

65Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests30 out of 30 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
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 34 contributing companies or organizations
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
7.5/7.5Maintained30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Branch-Protection, 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
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages70
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:leoric@2.16.0 runtime dependency closure — what installing the published package pulls in — 70 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.

75Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
15/15Machine-readable docs (llms.txt)llms.txt present
40/40Legible commit history95 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url
legible_history_share1
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes4,851
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc, .eslintrc.js
11/11Static type checkingtest/fixtures/ts49-consumer/tsconfig.json, test/fixtures/ts5-consumer/tsconfig.json, test/tsconfig.json, tsconfig.json
0/10Reproducible environment
10/10Demonstrated agent practice24 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_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstest/fixtures/ts49-consumer/tsconfig.json, test/fixtures/ts5-consumer/tsconfig.json, test/tsconfig.json, tsconfig.json
agent_commit_share0.24
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codeJavaScript with type-check config (test/fixtures/ts49-consumer/tsconfig.json, test/fixtures/ts5-consumer/tsconfig.json, test/tsconfig.json, tsconfig.json)
53.6/55Manageable file sizes4/153 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes221,629
source_files_sampled153
oversized_source_files4

Key facts

234GitHub stars
23contributors
58commits, last 12 months
31days since last push
100releases
1bus factor
1open issues
npm, RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 20 ⇿
0Stars
20Forks
73Releases

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.

0481216202022019-042021-072023-11
Major 1Minor 20Patch 52

Each point covers 5 days.

OpenSSF Scorecard 5.6 / 10
5.6aggregate

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-18 16:00 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 34 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
npmdayjs^1.10.3package.json
npmdebug^3.1.0package.json
npmdeep-equal^2.0.5package.json
npmpluralize^7.0.0package.json
npmreflect-metadata^0.1.13package.json
npmsqlstring^2.3.0package.json
npmtslib^2.5.0package.json
npmvalidator^13.5.2package.json
All dependencies 43

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

RegistryPackageVersionRelation
npmdayjs^1.10.3direct
npmdebug^3.1.0direct
npmdeep-equal^2.0.5direct
npmpluralize^7.0.0direct
npmreflect-metadata^0.1.13direct
npmsqlstring^2.3.0direct
npmtslib^2.5.0direct
npmvalidator^13.5.2direct
npm@babel/core^7.14.6indirect
npm@babel/eslint-parser^7.14.7indirect
npm@cara/minami^1.2.3indirect
npm@istanbuljs/nyc-config-typescript^1.0.2indirect
npm@journeyapps/sqlcipher^5.2.0indirect
npm@tsconfig/node18^18.2.4indirect
npm@types/debug^4.1.12indirect
npm@types/mocha^9.0.0indirect
npm@types/node^18.19.130indirect
npm@types/pluralize^0.0.33indirect
npm@types/sinon^10.0.20indirect
npm@types/sql.js^1.4.4indirect
npm@types/sqlstring^2.3.2indirect
npm@typescript-eslint/eslint-plugin^5.59.2indirect
npm@typescript-eslint/parser^5.59.2indirect
npmesbuild^0.28.1indirect
npmeslint^8.52.0indirect
npmeslint-plugin-no-only-tests^3.0.0indirect
npmexpect.js^0.3.1indirect
npmhusky^8.0.3indirect
npmjsdoc^4.0.2indirect
npmlint-staged^13.2.2indirect
npmmocha^10.2.0indirect
npmmysql^2.17.1indirect
npmmysql2^3.15.2indirect
npmnyc^15.1.0indirect
npmpg^8.5.1indirect
npmsinon^10.0.0indirect
npmsql.js^1.8.0indirect
npmsqlite3^5.0.2indirect
npmtaffydb^2.7.3indirect
npmts-node^10.9.2indirect
npmtypescript^5.9.2indirect
RubyGemsgithub-pagesindirect
RubyGemswebrickindirect
Dependency advisories 0

Installing npm:leoric@2.16.0 pulls in 70 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

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.