Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 00:25 UTC

js-soft / ts-linting

j&s-soft typescript linting rules

JavaScriptMIT★ 0 stars⑂ 0 forkssince Sep 2021View on GitHub ↗

js-soft/ts-linting holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (74/100) and lowest on Community & Adoption (35/100). It was last updated 1 day 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

js-softOrganization
8 followers35 public repossince Sep 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@js-soft/eslint-config-ts2.0.72,770671 day ago

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
6.2/36Commit cadence9/52 weeks with commits
10/18Commit volume12 commits in the last year
4/10OpenSSF Scorecard: Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year12
human_commit_share
days_since_last_push1
active_weeks_last_year9

Release discipline

100Exceptional
How it's scored
27/27Ships releases12 releases published
36/36Release recencylatest release 1 days ago
27/27Release cadencea release every ~40.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count12
latest_release_tag2.0.7
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases40.4
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?

35Weak · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars0
watchers1
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
45.9/80Monthly downloads2,770 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@js-soft/eslint-config-ts
dependents
ecosystemsnpm
total_downloads
monthly_downloads2,770
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?

71Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.5/22.5Commit distributiontop contributor authored 71% of commits
8.1/13.5Contributor breadth6 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.713
How it's scored
0/42Issue resolutionno issues or no data
30/30PR acceptance43/43 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 19/27 approved changesets -- score normalized to 7
Inputs used
merged_prs43
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
6.9/25Owner reach8 followers of js-soft
23.3/25Track record35 public repos, account ~8 yr old
Inputs used
followers8
owner_typeOrganization
is_verified
owner_loginjs-soft
public_repos35
account_age_days3,232
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 1 days ago
20/20Version history67 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@js-soft/eslint-config-ts
ecosystemsnpm
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter configeslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests13 out of 29 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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics1 topics
0/10Wiki
Inputs used
topicsfrosch
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?

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1/2.5CI-Tests13 out of 29 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-ReviewFound 19/27 approved changesets -- score normalized to 7
2.5/2.5Contributorsproject has 4 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
3/7.5Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
0/5Packagingno data
2.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
1/5SASTSAST tool is not run on all commits -- score normalized to 2
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

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.

49Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.mjs
11/11Static type checkingtest/tsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
5/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstest/tsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
27/45Type-checkable codeJavaScript with type-check config (test/tsconfig.json)
55/55Manageable file sizes0/8 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes7,297
source_files_sampled8
oversized_source_files0

Key facts

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

More detail

OpenSSF Scorecard 5.8 / 10
5.8aggregate

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

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
4CI-Tests13 out of 29 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 19/27 approved changesets -- score normalized to 7
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
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
n/aPackagingpackaging workflow not detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
2SASTSAST tool is not run on all commits -- score normalized to 2
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 6
RegistryPackageVersion constraintManifest
npm@eslint/js^9.39.4package.json
npmeslint-plugin-chai-expect^4.1.0package.json
npmeslint-plugin-chai-friendly^1.2.0package.json
npmeslint-plugin-jest^29.15.2package.json
npmeslint-plugin-mocha^11.3.0package.json
npmtypescript-eslint^8.59.4package.json
All dependencies 114

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

RegistryPackageVersionRelation
npm@eslint/js9.31.0direct
npm@eslint/js9.39.4direct
npmeslint-plugin-chai-expect4.1.0direct
npmeslint-plugin-chai-friendly1.2.0direct
npmeslint-plugin-jest29.15.2direct
npmeslint-plugin-mocha11.3.0direct
npmtypescript-eslint8.59.4direct
npm@aashutoshrathi/word-wrap1.2.6indirect
npm@eslint-community/eslint-utils4.9.1indirect
npm@eslint-community/regexpp4.12.2indirect
npm@eslint/config-array0.21.0indirect
npm@eslint/config-helpers0.3.0indirect
npm@eslint/core0.15.1indirect
npm@eslint/eslintrc3.3.1indirect
npm@eslint/object-schema2.1.6indirect
npm@eslint/plugin-kit0.3.4indirect
npm@humanfs/core0.19.1indirect
npm@humanfs/node0.16.6indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/retry0.3.1indirect
npm@humanwhocodes/retry0.4.3indirect
npm@types/estree1.0.8indirect
npm@types/json-schema7.0.15indirect
npm@typescript-eslint/eslint-plugin8.59.4indirect
npm@typescript-eslint/parser8.59.4indirect
npm@typescript-eslint/project-service8.59.4indirect
npm@typescript-eslint/scope-manager8.59.4indirect
npm@typescript-eslint/tsconfig-utils8.59.4indirect
npm@typescript-eslint/type-utils8.59.4indirect
npm@typescript-eslint/types8.59.4indirect
npm@typescript-eslint/typescript-estree8.59.4indirect
npm@typescript-eslint/utils8.59.4indirect
npm@typescript-eslint/visitor-keys8.59.4indirect
npmacorn8.15.0indirect
npmacorn-jsx5.3.2indirect
npmajv6.14.0indirect
npmansi-styles4.3.0indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion1.1.13indirect
npmbrace-expansion5.0.6indirect
npmcallsites3.1.0indirect
npmchalk4.1.2indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdeep-is0.1.4indirect
npmescape-string-regexp4.0.0indirect
npmeslint9.31.0indirect
npmeslint-scope8.4.0indirect
npmeslint-visitor-keys3.4.3indirect
npmeslint-visitor-keys4.2.1indirect
npmeslint-visitor-keys5.0.1indirect
npmespree10.4.0indirect
npmesquery1.5.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfdir6.5.0indirect
npmfile-entry-cache8.0.0indirect
npmfind-up5.0.0indirect
npmflat-cache4.0.1indirect
npmflatted3.4.2indirect
npmglob-parent6.0.2indirect
npmglobals14.0.0indirect
npmglobals15.15.0indirect
npmhas-flag4.0.0indirect
npmignore5.3.1indirect
npmignore7.0.5indirect
npmimport-fresh3.3.1indirect
npmimurmurhash0.1.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmisexe2.0.0indirect
npmjs-yaml4.3.0indirect
npmjson-buffer3.0.1indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmkeyv4.5.4indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmlodash.merge4.6.2indirect
npmminimatch10.2.5indirect
npmminimatch3.1.5indirect
npmms2.1.3indirect
npmnatural-compare1.4.0indirect
npmoptionator0.9.3indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmparent-module1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpicomatch4.0.4indirect
npmprelude-ls1.2.1indirect
npmpunycode2.3.1indirect
npmresolve-from4.0.0indirect
npmsemver7.8.1indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmtinyglobby0.2.16indirect
npmts-api-utils2.5.0indirect
npmtype-check0.4.0indirect
npmtypescript5.5.2indirect
npmuri-js4.4.1indirect
npmwhich2.0.2indirect
npmyocto-queue0.1.0indirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.