Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 16:08 UTC

itaymendel / oxlint-plugin-complexity

Cyclomatic and cognitive complexity rules for oxlint with actionable error messages. Also available as a standalone library for programmatic complexity analysis.

TypeScriptMIT★ 41 stars⑂ 3 forkssince Dec 2025View on GitHub ↗

itaymendel/oxlint-plugin-complexity holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (85/100) and lowest on Security (33/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Itay MendelawyPersonal account
26 followers6 public repossince Jun 2013@teambit

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
npmoxlint-plugin-complexity3.0.091,660250 days agooxlintoxceslintplugincomplexitycyclomaticcognitivecode-quality

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
13.8/36Commit cadence20/52 weeks with commits
18/18Commit volume118 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year118
human_commit_share0.52
days_since_last_push0
active_weeks_last_year20

Release discipline

100Exceptional
How it's scored
27/27Ships releases21 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~21.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count21
latest_release_tagv3.0.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases21.2

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

56Moderate · 17% of overall
How it's scored
26/60Stars41 stars
2.5/25Forks3 forks
0/15Watchers0 watchers
Inputs used
forks3
stars41
watchers0
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
66.2/80Monthly downloads91,660 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesoxlint-plugin-complexity
dependents
ecosystemsnpm
total_downloads
monthly_downloads91,660
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution100% of issues closed
15/30PR acceptance78/156 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs78
open_issues0
closed_issues4
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs78
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
10.3/25Owner reach26 followers of itaymendel
18.2/25Track record6 public repos, account ~13 yr old
Inputs used
followers26
owner_typeUser
is_verified
owner_loginitaymendel
public_repos6
account_age_days4,848
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 0 days ago
20/20Version history25 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesoxlint-plugin-complexity
ecosystemsnpm
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows3 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

Documentation

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

33At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfilespublished library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilespnpm-lock.yaml
manifestspackage.json
has_codeql_workflowno
has_security_policyno
has_dependabot_configyes
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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.

69Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://oxc.rs/llms.txt)
40/40Legible commit history49 of 52 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://oxc.rs/llms.txt
legible_history_share0.942
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
10/10Demonstrated agent practice5 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance48 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0.05
toolchain_manifests
dependency_bot_commit_share0.48
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/102 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes16,504
source_files_sampled102
oversized_source_files0

Key facts

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

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index npm:oxlint-plugin-complexity@3.0.0; advisories assessed against the repository dependency graph instead
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/itaymendel/oxlint-plugin-complexity: run: RepoClient.LocalPath: error during tarballHandler.setup: internal error: handler.httpClient.Do: Get "https://codeload.github.com/itaymendel/oxlint-plugin-complexity/legacy.tar.gz/refs/heads/main": internal error: innerTransport.RoundTrip: internal error: innerTransport.RoundTrip: error in HTTP: dial tcp: lookup codeload.github.com on 127.0.0.11:53: server misbehaving); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 3 ⇿
0Stars
3Forks
20Releases

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.

12233312025-122026-052026-09
Major 2Minor 3Patch 15
Direct dependencies 1
RegistryPackageVersion constraintManifest
npm@oxlint/plugins^1.73.0package.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

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.