Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 12:41 UTC

rowanmanning / varname

Convert strings between different variable naming formats.

TypeScriptMIT★ 1 star⑂ 0 forkssince Jul 2023View on GitHub ↗

rowanmanning/varname holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (73/100) and lowest on Sustainability & Governance (51/100). It was last updated 8 days ago. A single contributor accounts for most of its recent work.

67
overall / 100
Good

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.

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

Ownership

Rowan ManningPersonal account
255 followers102 public repossince Oct 2009@Financial-Times

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
npmvarname8.1.0188,6442840 days agocamelcasecamelbacknamingstringvariable

Metrics by category

Vitality

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

63Moderate · 21% of overall
How it's scored
28.8/36Push recency — last push 8 days ago
1.4/36Commit cadence — 2/52 weeks with commits
11.1/18Commit volume — 16 commits in the last year
8/10OpenSSF Scorecard: Maintained — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year16
human_commit_share0.48
days_since_last_push8
active_weeks_last_year2
How it's scored
27/27Ships releases — 9 releases published
36/36Release recency — latest release 40 days ago
12.6/27Release cadence — a release every ~143 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count9
latest_release_tagv8.1.0
releases_from_tagsno
days_since_latest_release40
mean_days_between_releases143
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?

52Moderate · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars1
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
70.3/80Monthly downloads — 188,644 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesvarname
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads188,644
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?

51Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.6/22.5Commit distribution — top contributor authored 97% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.972
How it's scored
0/42Issue resolution — no issues or no data
13.8/30PR acceptance — 73/159 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/13 approved changesets -- score normalized to 0
Inputs used
merged_prs73
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs86
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
17.3/25Owner reach — 255 followers of rowanmanning
25/25Track record — 102 public repos, account ~17 yr old
Inputs used
followers255
owner_typeUser
is_verified—
owner_loginrowanmanning
public_repos102
account_age_days6,217
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 40 days ago
20/20Version history — 28 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesvarname
ecosystemsnpm
any_deprecatedno
min_days_since_publish40

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests — 9 out of 20 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 1 topics
0/10Wiki
Inputs used
topicslibrary
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

71Good · 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
1/2.5CI-Tests — 9 out of 20 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/13 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
6/7.5Maintained — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
2.5/5SAST — SAST tool is not run on all commits -- score normalized to 5
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.4
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 advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages112
unassessed_packages0
affected_by_severitymoderate 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 112 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.

61Moderate · 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 — 48 of 48 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — biome.json
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 48 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.48
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/2 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes2,674
source_files_sampled2
oversized_source_files0

Key facts

1GitHub stars
3contributors
16commits, last 12 months
8days since last push
9releases
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 6.4 / 10
6.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-10-21 12:41 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
4CI-Tests9 out of 20 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/13 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5SASTSAST tool is not run on all commits -- score normalized to 5
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 112

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

RegistryPackageVersionRelation
npm@babel/code-frame7.29.7indirect
npm@babel/helper-validator-identifier7.29.7indirect
npm@biomejs/biome2.5.13indirect
npm@biomejs/cli-darwin-arm642.5.13indirect
npm@biomejs/cli-darwin-x642.5.13indirect
npm@biomejs/cli-linux-arm642.5.13indirect
npm@biomejs/cli-linux-arm64-musl2.5.13indirect
npm@biomejs/cli-linux-x642.5.13indirect
npm@biomejs/cli-linux-x64-musl2.5.13indirect
npm@biomejs/cli-win32-arm642.5.13indirect
npm@biomejs/cli-win32-x642.5.13indirect
npm@commitlint/cli20.5.3indirect
npm@commitlint/config-conventional20.5.3indirect
npm@commitlint/config-validator20.5.0indirect
npm@commitlint/ensure20.5.3indirect
npm@commitlint/execute-rule20.0.0indirect
npm@commitlint/format20.5.0indirect
npm@commitlint/is-ignored20.5.0indirect
npm@commitlint/lint20.5.3indirect
npm@commitlint/load20.5.3indirect
npm@commitlint/message20.4.3indirect
npm@commitlint/parse20.5.0indirect
npm@commitlint/read20.5.0indirect
npm@commitlint/resolve-extends20.5.3indirect
npm@commitlint/rules20.5.3indirect
npm@commitlint/to-lines20.0.0indirect
npm@commitlint/top-level20.4.3indirect
npm@commitlint/types20.5.0indirect
npm@conventional-changelog/git-client2.7.0indirect
npm@rowanmanning/biome-config3.1.0indirect
npm@simple-libs/child-process-utils1.0.2indirect
npm@simple-libs/stream-utils1.2.0indirect
npm@types/node22.20.2indirect
npm@typescript/typescript-aix-ppc647.0.2indirect
npm@typescript/typescript-darwin-arm647.0.2indirect
npm@typescript/typescript-darwin-x647.0.2indirect
npm@typescript/typescript-freebsd-arm647.0.2indirect
npm@typescript/typescript-freebsd-x647.0.2indirect
npm@typescript/typescript-linux-arm7.0.2indirect
npm@typescript/typescript-linux-arm647.0.2indirect
npm@typescript/typescript-linux-loong647.0.2indirect
npm@typescript/typescript-linux-mips64el7.0.2indirect
npm@typescript/typescript-linux-ppc647.0.2indirect
npm@typescript/typescript-linux-riscv647.0.2indirect
npm@typescript/typescript-linux-s390x7.0.2indirect
npm@typescript/typescript-linux-x647.0.2indirect
npm@typescript/typescript-netbsd-arm647.0.2indirect
npm@typescript/typescript-netbsd-x647.0.2indirect
npm@typescript/typescript-openbsd-arm647.0.2indirect
npm@typescript/typescript-openbsd-x647.0.2indirect
npm@typescript/typescript-sunos-x647.0.2indirect
npm@typescript/typescript-win32-arm647.0.2indirect
npm@typescript/typescript-win32-x647.0.2indirect
npmajv8.20.0indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmargparse2.0.1indirect
npmarray-ify1.0.0indirect
npmcallsites3.1.0indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcompare-func2.0.0indirect
npmconventional-changelog-angular8.3.1indirect
npmconventional-changelog-conventionalcommits9.3.1indirect
npmconventional-commits-parser6.4.0indirect
npmcosmiconfig9.0.2indirect
npmcosmiconfig-typescript-loader6.3.0indirect
npmdot-prop5.3.0indirect
npmemoji-regex8.0.0indirect
npmenv-paths2.2.1indirect
npmerror-ex1.3.4indirect
npmes-toolkit1.52.0indirect
npmescalade3.2.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-uri3.1.7indirect
npmget-caller-file2.0.5indirect
npmgit-raw-commits5.0.1indirect
npmglobal-directory5.0.0indirect
npmhusky9.1.7indirect
npmimport-fresh3.3.1indirect
npmimport-meta-resolve4.2.0indirect
npmini6.0.0indirect
npmis-arrayish0.2.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-obj2.0.0indirect
npmis-plain-obj4.1.0indirect
npmjiti2.6.1indirect
npmjs-tokens4.0.0indirect
npmjs-yaml4.3.2indirect
npmjson-parse-even-better-errors2.3.1indirect
npmjson-schema-traverse1.0.0indirect
npmlines-and-columns1.2.4indirect
npmmeow13.2.0indirect
npmminimist1.2.8indirect
npmparent-module1.0.1indirect
npmparse-json5.2.0indirect
npmpicocolors1.1.1indirect
npmrequire-directory2.1.1indirect
npmrequire-from-string2.0.2indirect
npmresolve-from4.0.0indirect
npmresolve-from5.0.0indirect
npmsemver7.8.5indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmtinyexec1.3.1indirect
npmtypescript7.0.2indirect
npmundici-types6.21.0indirect
npmwrap-ansi7.0.0indirect
npmy18n5.0.8indirect
npmyargs17.7.3indirect
npmyargs-parser21.1.1indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
fast-uri3.1.7indirectmoderate14.1.5

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 statistics — npm.