Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 15:19 UTC

scalar / formatters

Wasm based formatters for targets missing from wasm-fmt

TypeScript · JavaScriptCustom license★ 1 star⑂ 0 forkssince Aug 2026View on GitHub ↗
KindLibraryApplicationhow this is determined

scalar/formatters holds a health index of 78 out of 100, placing it in the Good band. It scores highest on AI Readiness (92/100) and lowest on Community & Adoption (47/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

ScalarOrganization · verified domain
414 followers33 public repossince Jun 2010

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

Metrics by category

Vitality

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

73Good · 21% of overall
How it's scored
36/36Push recencylast push 6 days ago
4.2/36Commit cadence6/52 weeks with commits
14.8/18Commit volume44 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year44
human_commit_share0.659
days_since_last_push6
active_weeks_last_year6

Release discipline

100Exceptional
How it's scored
27/27Ships releases23 releases published
36/36Release recencylatest release 6 days ago
27/27Release cadencea release every ~2.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count23
latest_release_tag@scalar/ruby-fmt@0.6.3
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases2.5
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?

47Weak · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
70.4/80Monthly downloads191,480 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@scalar/php-fmt, @scalar/java-fmt, @scalar/ruby-fmt, @scalar/rust-fmt, @scalar/swift-fmt, @scalar/csharp-fmt, @scalar/kotlin-fmt
dependents
ecosystemsnpm
total_downloads
monthly_downloads191,480
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?

72Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.1/22.5Commit distributiontop contributor authored 86% of commits
4.1/13.5Contributor breadth3 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.862
How it's scored
0/42Issue resolutionno issues or no data
30/30PR acceptance38/38 decided PRs merged
13/13Newcomer PR acceptance3/3 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 17/19 approved changesets -- score normalized to 8
Inputs used
merged_prs38
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d12
prs_decided_30d12
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d1
first_time_prs_merged_30d3
first_time_prs_decided_30d3
Excluded from scoring (no data or not applicable): Issue resolution. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
18.8/25Owner reach414 followers of scalar
23.2/25Track record33 public repos, account ~16 yr old
Inputs used
followers414
owner_typeOrganization
is_verifiedyes
owner_loginscalar
public_repos33
account_age_days5,944

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable7 package(s) on npm
35/35Publish recencylatest publish 6 days ago
20/20Version history10 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@scalar/php-fmt, @scalar/java-fmt, @scalar/ruby-fmt, @scalar/rust-fmt, @scalar/swift-fmt, @scalar/csharp-fmt, @scalar/kotlin-fmt
ecosystemsnpm
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests21 out of 30 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
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?

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1.8/2.5CI-Tests21 out of 30 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6/7.5Code-ReviewFound 17/19 approved changesets -- score normalized to 8
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
0/5Packagingno data
5/5Pinned-Dependenciesall dependencies are pinned
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
5.2/7.5Vulnerabilities3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.7
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
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_packages8
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:@scalar/php-fmt@0.4.0 runtime dependency closure — what installing the published package pulls in — 8 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.

92Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history29 of 29 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes4,823
How it's scored
12.6/18One-command bootstrapbuild/csharp_fmt/csharp_fmt.csproj, build/java_fmt_teavm/classlib-probe/pom.xml, build/java_fmt_teavm/kotlin-probe/pom.xml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingpackages/csharp/tsconfig.json, packages/java/tsconfig.json, packages/kotlin/tsconfig.json, packages/php/tsconfig.json, packages/ruby/tsconfig.json, packages/rust/tsconfig.json, packages/swift/tsconfig.json, tsconfig.json
10/10Reproducible environmentlockfile
10/10Demonstrated agent practice14 of the last 44 commits agent-authored or agent-credited
8/8Automated maintenance4 of the last 44 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configspackages/csharp/tsconfig.json, packages/java/tsconfig.json, packages/kotlin/tsconfig.json, packages/php/tsconfig.json, packages/ruby/tsconfig.json, packages/rust/tsconfig.json, packages/swift/tsconfig.json, tsconfig.json
agent_commit_share0.318
toolchain_manifestsbuild/csharp_fmt/csharp_fmt.csproj, build/java_fmt_teavm/classlib-probe/pom.xml, build/java_fmt_teavm/kotlin-probe/pom.xml, build/java_fmt_teavm/kotlin-probe/teavm-bug/pom.xml, build/java_fmt_teavm/pom.xml, build/rust_fmt/crates/rust_fmt/Cargo.toml
dependency_bot_commit_share0.091
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.2/55Manageable file sizes2/134 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes220,892
source_files_sampled134
oversized_source_files2

Key facts

1GitHub stars
3contributors
44commits, last 12 months
6days since last push
23releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package '@scalar/formatters' from its registry
  • Could not fetch maven package 'local.javafmt:java-fmt-wasm' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 6.7 / 10
6.7aggregate

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 15:18 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
7CI-Tests21 out of 30 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 17/19 approved changesets -- score normalized to 8
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 26
RegistryPackageVersion constraintManifest
npmlefthook^2.1.12package.json
NuGetCSharpier.Core$(CSharpierVersion)build/csharp_fmt/csharp_fmt.csproj
Mavenorg.teavm:teavm-classlib${teavm.version}build/java_fmt_teavm/pom.xml
Mavenorg.teavm:teavm-jso-apis${teavm.version}build/java_fmt_teavm/pom.xml
Mavenorg.openjdk:jdk-compiler21build/java_fmt_teavm/pom.xml
Mavenlocal.javafmt:google-java-format-patched${gjf.version}build/java_fmt_teavm/pom.xml
Mavenlocal.javafmt:teavm-stubs1build/java_fmt_teavm/pom.xml
RubyGemssyntax_tree6.3.0build/ruby_fmt/Gemfile
RubyGemsrubocop1.81.6build/ruby_fmt/Gemfile
RubyGemsrubocop-ast1.50.0build/ruby_fmt/Gemfile
RubyGemsjsonbuild/ruby_fmt/Gemfile
RubyGemsprismbuild/ruby_fmt/Gemfile
RubyGemsjs2.10.1build/ruby_fmt/Gemfile
RubyGemsruby_wasm2.10.1build/ruby_fmt/Gemfile
npmbrotli-dec-wasm^2.3.2packages/csharp/package.json
npmbrotli-dec-wasm^2.3.2packages/java/package.json
npmbrotli-dec-wasm^2.3.2packages/kotlin/package.json
npm@php-wasm/node-8-43.1.47packages/php/package.json
npm@php-wasm/universal3.1.47packages/php/package.json
npm@bjorn3/browser_wasi_shim^0.4.2packages/ruby/package.json
npm@ruby/wasm-wasi^2.8.1packages/ruby/package.json
npmbrotli-dec-wasm^2.3.2packages/ruby/package.json
npm@bjorn3/browser_wasi_shim^0.4.2packages/rust/package.json
npmbrotli-dec-wasm^2.3.2packages/rust/package.json
npm@bjorn3/browser_wasi_shim^0.4.2packages/swift/package.json
npmbrotli-dec-wasm^2.3.2packages/swift/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 0

Installing npm:@scalar/php-fmt@0.4.0 pulls in 8 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.