Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-31 10:48 UTC

slevithan / oniguruma-to-es

👹 Convert patterns from Oniguruma (the regex flavor used by Ruby, TextMate grammars, etc.) to native JavaScript RegExp

JavaScriptMIT★ 149 stars⑂ 6 forkssince Sep 2024View on GitHub ↗

slevithan/oniguruma-to-es holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (68/100) and lowest on AI Readiness (26/100). It was last updated 133 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Steven LevithanPersonal account
669 followers18 public repossince Feb 2012

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
npmoniguruma-to-es4.3.665,591,82036133 days agoregexregexponigurumatextmate-grammartranspiler

Metrics by category

Vitality

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

48Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 133 days ago
3.5/36Commit cadence5/52 weeks with commits
11.5/18Commit volume18 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year18
human_commit_share1
days_since_last_push133
active_weeks_last_year5
How it's scored
27/27Ships releases33 releases published
27/36Release recencylatest release 133 days ago
19.8/27Release cadencea release every ~45.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count33
latest_release_tagv4.3.6
releases_from_tagsno
days_since_latest_release133
mean_days_between_releases45.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?

68Good · 17% of overall
How it's scored
35.2/60Stars149 stars
5.8/25Forks6 forks
3.9/15Watchers6 watchers
Inputs used
forks6
stars149
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Monthly downloads65,591,820 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesoniguruma-to-es
dependents
ecosystemsnpm
total_downloads
monthly_downloads65,591,820
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.2/22.5Commit distributiontop contributor authored 99% of commits
9.5/13.5Contributor breadth7 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.991
How it's scored
38.4/42Issue resolution91% of issues closed
22.5/30PR acceptance6/8 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 2/30 approved changesets -- score normalized to 0
Inputs used
merged_prs6
open_issues3
closed_issues32
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.914
closed_unmerged_prs2
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
20.3/25Owner reach669 followers of slevithan
21.3/25Track record18 public repos, account ~14 yr old
Inputs used
followers669
owner_typeUser
is_verified
owner_loginslevithan
public_repos18
account_age_days5,302
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 133 days ago
20/20Version history36 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesoniguruma-to-es
ecosystemsnpm
any_deprecatedno
min_days_since_publish133

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://slevithan.github.io/oniguruma-to-es/demo/
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsoniguruma, regex, textmate-grammar, transpiler
has_wikino
homepagehttps://slevithan.github.io/oniguruma-to-es/demo/
docs_sitehttps://slevithan.github.io/oniguruma-to-es/demo/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests2 out of 2 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
0/7.5Code-ReviewFound 2/30 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
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/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
3.8/7.5Vulnerabilities5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.1
Excluded from scoring (no data or not applicable): 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
advisories5
affected_packages2
assessed_packages43
unassessed_packages0
affected_by_severityhigh 1, low 1
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 43 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.

26At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
3.2/40Legible commit history6 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.06
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
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
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/35 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes39,579
source_files_sampled35
oversized_source_files0

Key facts

149GitHub stars
7contributors
18commits, last 12 months
133days since last push
33releases
1bus factor
3open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index npm:oniguruma-to-es@4.3.6; advisories assessed against the repository dependency graph instead

More detail

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

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.

123456612024-112025-072026-03
Major 4Minor 13Patch 8

Each point covers 2 days.

OpenSSF Scorecard 3.1 / 10
3.1aggregate

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-08-31 10:48 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
5Vulnerabilities5 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmoniguruma-parser^0.12.2package.json
npmregex^6.1.0package.json
npmregex-recursion^6.0.2package.json
All dependencies 43

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

RegistryPackageVersionRelation
npmoniguruma-parser0.12.2direct
npmregex6.1.0direct
npmregex-recursion6.0.2direct
npm@esbuild/aix-ppc640.28.0indirect
npm@esbuild/android-arm0.28.0indirect
npm@esbuild/android-arm640.28.0indirect
npm@esbuild/android-x640.28.0indirect
npm@esbuild/darwin-arm640.28.0indirect
npm@esbuild/darwin-x640.28.0indirect
npm@esbuild/freebsd-arm640.28.0indirect
npm@esbuild/freebsd-x640.28.0indirect
npm@esbuild/linux-arm0.28.0indirect
npm@esbuild/linux-arm640.28.0indirect
npm@esbuild/linux-ia320.28.0indirect
npm@esbuild/linux-loong640.28.0indirect
npm@esbuild/linux-mips64el0.28.0indirect
npm@esbuild/linux-ppc640.28.0indirect
npm@esbuild/linux-riscv640.28.0indirect
npm@esbuild/linux-s390x0.28.0indirect
npm@esbuild/linux-x640.28.0indirect
npm@esbuild/netbsd-arm640.28.0indirect
npm@esbuild/netbsd-x640.28.0indirect
npm@esbuild/openbsd-arm640.28.0indirect
npm@esbuild/openbsd-x640.28.0indirect
npm@esbuild/openharmony-arm640.28.0indirect
npm@esbuild/sunos-x640.28.0indirect
npm@esbuild/win32-arm640.28.0indirect
npm@esbuild/win32-ia320.28.0indirect
npm@esbuild/win32-x640.28.0indirect
npm@jasminejs/reporters1.0.0indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.5indirect
npmesbuild0.28.0indirect
npmglob13.0.6indirect
npmjasmine6.2.0indirect
npmjasmine-core6.2.0indirect
npmlru-cache11.3.5indirect
npmminimatch10.2.5indirect
npmminipass7.1.3indirect
npmpath-scurry2.0.2indirect
npmregex-utilities2.3.0indirect
npmtypescript6.0.3indirect
npmvscode-oniguruma2.0.1indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion5.0.5indirecthigh45.0.9
esbuild0.28.0indirectlow10.28.1

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.