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

senoff / xlsx-for-ai

MCP server + CLI giving AI agents 50 spreadsheet tools for .xlsx — live-recalc formulas (~390 Excel functions), repair broken references & external links, read/write, diff, and audit. Works in Claude Code, Cursor, Codex, and any MCP client.

JavaScriptMIT★ 6 stars⑂ 0 forkssince Apr 2026View on GitHub ↗
KindCommand-line toolLibraryMCP serverhow this is determined

senoff/xlsx-for-ai holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Security (84/100) and lowest on Community & Adoption (36/100). It was last updated 1 day 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

senoffPersonal account
2 followers15 public repossince Apr 2013

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
npmxlsx-for-ai4.0.32,047721 day agoxlsxexcelaimcpclaudecursorcopilotchatgptllmagentspreadsheetjsonmcp-server

Metrics by category

Vitality

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

80Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
11.8/36Commit cadence — 17/52 weeks with commits
18/18Commit volume — 274 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year274
human_commit_share0.92
days_since_last_push1
active_weeks_last_year17
How it's scored
27/27Ships releases — 10 releases published
27/36Release recency — latest release 92 days ago
27/27Release cadence — a release every ~3.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count10
latest_release_tagv3.0.16
releases_from_tagsno
days_since_latest_release92
mean_days_between_releases3.5

Community & Adoption

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

36Weak · 17% of overall
How it's scored
11.3/60Stars — 6 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars6
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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
44.2/80Monthly downloads — 2,047 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesxlsx-for-ai
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,047
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — no issues or no data
26/30PR acceptance — 59/68 decided PRs merged
12.2/13Newcomer PR acceptance — 16/17 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs59
open_issues0
closed_issues0
prs_merged_7d6
prs_decided_7d7
prs_merged_30d16
prs_decided_30d17
issue_closed_ratio—
closed_unmerged_prs9
first_time_authors_30d1
first_time_prs_merged_30d16
first_time_prs_decided_30d17
Excluded from scoring (no data or not applicable): Issue resolution. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
3.4/25Owner reach — 2 followers of senoff
20.8/25Track record — 15 public repos, account ~13 yr old
Inputs used
followers2
owner_typeUser
is_verified—
owner_loginsenoff
public_repos15
account_age_days4,885
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 1 days ago
20/20Version history — 72 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesxlsx-for-ai
ecosystemsnpm
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 8 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://xlsx-for-ai.dev
10/10Repository description
10/10Topics — 12 topics
10/10Wiki
Inputs used
topicsagent, ai, claude, cli, copilot, cursor, excel, llm, spreadsheet, xlsx, mcp, mcp-server
has_wikiyes
homepagehttps://xlsx-for-ai.dev
docs_sitehttps://xlsx-for-ai.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

84Excellent · 16% of overall

Security posture

80Excellent
How it's scored
30/30Security policy (SECURITY.md)
25/25Dependabot config
25/25Dependency lockfiles — package-lock.json
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilespackage-lock.json
manifestspackage.json
has_codeql_workflowno
has_security_policyyes
has_dependabot_configyes

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages95
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:xlsx-for-ai@4.0.3 runtime dependency closure — what installing the published package pulls in — 95 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.

69Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 91 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.989
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes5,463
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 63 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.63
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
53.9/55Manageable file sizes — 1/49 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes131,028
source_files_sampled49
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
40/40Runnable examples — samples
Inputs used
example_dirssamples
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

6GitHub stars
1contributors
274commits, last 12 months
1days since last push
10releases
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
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/senoff/xlsx-for-ai: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-09-09T14:14:19Z. Please include `C432:285674:1620D4E:156B66E:6AA169B9` when reporting this issue.); skipping Scorecard checks

More detail

Direct dependencies 1
RegistryPackageVersion constraintManifest
npm@modelcontextprotocol/sdk^1.29.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

Dependency advisories 0

Installing npm:xlsx-for-ai@4.0.3 pulls in 95 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 statistics — npm.