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

slevithan / regex

JS regexes ➕ future. A template tag for readable, high-performance, native JS regexes with extended syntax, context-aware interpolation, and always-on best practices.

JavaScriptMIT★ 632 stars⑂ 15 forkssince May 2024View on GitHub ↗

slevithan/regex holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (66/100) and lowest on AI Readiness (25/100). It was last updated 110 days ago. A single contributor accounts for most of its recent work.

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

54
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 53 is calibrated to 54 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
npmregex6.1.066,694,79329265 days agoregexregexp

Metrics by category

Vitality

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

46Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 110 days ago
6.2/36Commit cadence9/52 weeks with commits
12.7/18Commit volume25 commits in the last year
1/10OpenSSF Scorecard: Maintained0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year25
human_commit_share1
days_since_last_push110
active_weeks_last_year9
How it's scored
27/27Ships releases27 releases published
16.2/36Release recencylatest release 265 days ago
19.8/27Release cadencea release every ~48 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count27
latest_release_tagv6.1.0
releases_from_tagsno
days_since_latest_release265
mean_days_between_releases48
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?

66Good · 17% of overall
How it's scored
45.4/60Stars632 stars
9.6/25Forks15 forks
3.3/15Watchers5 watchers
Inputs used
forks15
stars632
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
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
80/80Monthly downloads66,694,793 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesregex
dependents
ecosystemsnpm
total_downloads
monthly_downloads66,694,793
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.4/22.5Commit distributiontop contributor authored 98% of commits
10.8/13.5Contributor breadth8 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.982
How it's scored
40.4/42Issue resolution96% of issues closed
24/30PR acceptance8/10 decided PRs merged
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_prs8
open_issues1
closed_issues26
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.963
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.
How it's scored
25/25Published & resolvable1 package(s) on npm
26/35Publish recencylatest publish 265 days ago
20/20Version history29 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesregex
ecosystemsnpm
any_deprecatedno
min_days_since_publish265

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 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
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicsregex, regular-expression
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

41Weak · 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/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.8/7.5Maintained0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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
3/7.5Vulnerabilities6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate2.6
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
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_packages1
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:regex@6.1.0 runtime dependency closure — what installing the published package pulls in — 1 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.

25At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
1.1/40Legible commit history2 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.02
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/29 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes15,800
source_files_sampled29
oversized_source_files0

Key facts

632GitHub stars
8contributors
25commits, last 12 months
110days since last push
27releases
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 ★ / 15 ⇿
0Stars
15Forks
23Releases

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.

03581013151512024-062024-122025-06
Major 5Minor 7Patch 11
OpenSSF Scorecard 2.6 / 10
2.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-08-31 10:48 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
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmregex-utilities^2.3.0package.json
All dependencies 95

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

RegistryPackageVersionRelation
npmregex-utilities2.3.0direct
npm@andrewbranch/untar.js1.0.3indirect
npm@arethetypeswrong/cli0.18.2indirect
npm@arethetypeswrong/core0.18.2indirect
npm@braidai/lang1.1.2indirect
npm@colors/colors1.5.0indirect
npm@esbuild/aix-ppc640.27.3indirect
npm@esbuild/android-arm0.27.3indirect
npm@esbuild/android-arm640.27.3indirect
npm@esbuild/android-x640.27.3indirect
npm@esbuild/darwin-arm640.27.3indirect
npm@esbuild/darwin-x640.27.3indirect
npm@esbuild/freebsd-arm640.27.3indirect
npm@esbuild/freebsd-x640.27.3indirect
npm@esbuild/linux-arm0.27.3indirect
npm@esbuild/linux-arm640.27.3indirect
npm@esbuild/linux-ia320.27.3indirect
npm@esbuild/linux-loong640.27.3indirect
npm@esbuild/linux-mips64el0.27.3indirect
npm@esbuild/linux-ppc640.27.3indirect
npm@esbuild/linux-riscv640.27.3indirect
npm@esbuild/linux-s390x0.27.3indirect
npm@esbuild/linux-x640.27.3indirect
npm@esbuild/netbsd-arm640.27.3indirect
npm@esbuild/netbsd-x640.27.3indirect
npm@esbuild/openbsd-arm640.27.3indirect
npm@esbuild/openbsd-x640.27.3indirect
npm@esbuild/openharmony-arm640.27.3indirect
npm@esbuild/sunos-x640.27.3indirect
npm@esbuild/win32-arm640.27.3indirect
npm@esbuild/win32-ia320.27.3indirect
npm@esbuild/win32-x640.27.3indirect
npm@jasminejs/reporters1.0.0indirect
npm@loaderkit/resolve1.0.4indirect
npm@sindresorhus/is4.6.0indirect
npmansi-escapes7.3.0indirect
npmansi-regex5.0.1indirect
npmansi-regex6.2.2indirect
npmansi-styles4.3.0indirect
npmany-promise1.3.0indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.4indirect
npmchalk4.1.2indirect
npmchalk5.6.2indirect
npmchar-regex1.0.2indirect
npmcjs-module-lexer1.4.3indirect
npmcli-highlight2.1.11indirect
npmcli-table30.6.5indirect
npmcliui7.0.4indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcommander10.0.1indirect
npmemoji-regex8.0.0indirect
npmemojilib2.4.0indirect
npmenvironment1.1.0indirect
npmesbuild0.27.3indirect
npmescalade3.2.0indirect
npmexpect-type1.3.0indirect
npmfflate0.8.2indirect
npmget-caller-file2.0.5indirect
npmglob13.0.6indirect
npmhas-flag4.0.0indirect
npmhighlight.js10.7.3indirect
npmis-fullwidth-code-point3.0.0indirect
npmjasmine6.1.0indirect
npmjasmine-core6.1.0indirect
npmlru-cache11.2.6indirect
npmmarked9.1.6indirect
npmmarked-terminal7.3.0indirect
npmminimatch10.2.4indirect
npmminipass7.1.3indirect
npmmz2.7.0indirect
npmnode-emoji2.2.0indirect
npmobject-assign4.1.1indirect
npmparse55.1.1indirect
npmparse56.0.1indirect
npmparse5-htmlparser2-tree-adapter6.0.1indirect
npmpath-scurry2.0.2indirect
npmrequire-directory2.1.1indirect
npmsemver7.7.4indirect
npmskin-tone2.0.0indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmsupports-color7.2.0indirect
npmsupports-hyperlinks3.2.0indirect
npmthenify3.3.1indirect
npmthenify-all1.6.0indirect
npmtypescript5.6.1-rcindirect
npmtypescript5.9.3indirect
npmunicode-emoji-modifier-base1.0.0indirect
npmvalidate-npm-package-name5.0.1indirect
npmwrap-ansi7.0.0indirect
npmy18n5.0.8indirect
npmyargs16.2.0indirect
npmyargs-parser20.2.9indirect
Dependency advisories 0

Installing npm:regex@6.1.0 pulls in 1 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.