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

Akshat2634 / Codelens-AI

Local-first ROI analytics for Claude Code, OpenAI Codex, and GitHub Copilot

JavaScript · HTMLMIT★ 11 stars⑂ 3 forkssince Feb 2026View on GitHub ↗
KindCommand-line toolLibraryMCP serverNetwork servicehow this is determined

Akshat2634/Codelens-AI holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (83/100) and lowest on Sustainability & Governance (52/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.

81
overall / 100
Excellent

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.

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

Ownership

Akshat SahuPersonal account
14 followers49 public repossince Oct 2020Futurepath AI

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
npmcodelens-ai0.10.39613923 days agocodelensclaudecodexcopilotgithub-copilotcursorairoiproductivitytokenscostgitdashboard

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recency — last push 6 days ago
8.3/36Commit cadence — 12/52 weeks with commits
18/18Commit volume — 231 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year231
human_commit_share0.92
days_since_last_push6
active_weeks_last_year12

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 45 releases published
36/36Release recency — latest release 23 days ago
27/27Release cadence — a release every ~4.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count45
latest_release_tagv0.10.3
releases_from_tagsno
days_since_latest_release23
mean_days_between_releases4.2
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
16.2/60Stars — 11 stars
2.5/25Forks — 3 forks
0/15Watchers — 0 watchers
Inputs used
forks3
stars11
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
39.8/80Monthly downloads — 961 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescodelens-ai
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads961
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?

52Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.8/22.5Commit distribution — top contributor authored 52% of commits
4.1/13.5Contributor breadth — 3 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.52
How it's scored
9.3/42Issue resolution — 22% of issues closed
25.3/30PR acceptance — 86/102 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/22 approved changesets -- score normalized to 0
Inputs used
merged_prs86
open_issues7
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d8
prs_decided_30d9
issue_closed_ratio0.222
closed_unmerged_prs16
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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
8.5/25Owner reach — 14 followers of Akshat2634
24.2/25Track record — 49 public repos, account ~5 yr old
Inputs used
followers14
owner_typeUser
is_verified—
owner_loginAkshat2634
public_repos49
account_age_days2,161
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 23 days ago
20/20Version history — 39 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescodelens-ai
ecosystemsnpm
any_deprecatedno
min_days_since_publish23

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 23 out of 23 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://codelensai-dev.vercel.app
10/10Repository description
10/10Topics — 11 topics
10/10Wiki
Inputs used
topicsclaude-ai, claude-code, claude-code-skills, ai-coding, analytics, cli, developer-tools, github-copilot, local-first, nodejs, openai-codex
has_wikiyes
homepagehttps://codelensai-dev.vercel.app
docs_sitehttps://codelensai-dev.vercel.app
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

78Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/22 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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
7.5/7.5Maintained — 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
4.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
4/5SAST — SAST tool detected but not run on all commits
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
0.8/7.5Vulnerabilities — 9 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.3
Excluded from scoring (no data or not applicable): Branch-Protection, 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
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_packages109
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:codelens-ai@0.10.3 runtime dependency closure — what installing the published package pulls in — 109 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
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://platform.claude.com/llms.txt)
39.4/40Legible commit history — 68 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://platform.claude.com/llms.txt
legible_history_share0.739
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes17,122
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — biome.json
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 52 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 7 of the last 100 commits are automated dependency updates
9/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.52
toolchain_manifests—
dependency_bot_commit_share0.07
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
53.7/55Manageable file sizes — 1/42 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes68,576
source_files_sampled42
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

11GitHub stars
3contributors
231commits, last 12 months
6days since last push
45releases
1bus factor
7open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

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

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.

1223344412026-032026-052026-08
Major 0Minor 4Patch 33
OpenSSF Scorecard 7.3 / 10
7.3aggregate

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-09 21:40 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/22 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
8SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
1Vulnerabilities9 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npm@modelcontextprotocol/sdk^1.30.0package.json
npmcommander^15.0.0package.json
npmexpress^5.0.0package.json
npmopen^11.0.0package.json
All dependencies 120

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

RegistryPackageVersionRelation
npm@modelcontextprotocol/sdk1.30.0direct
npmcommander15.0.0direct
npmexpress5.2.1direct
npmopen11.0.0direct
npm@biomejs/biome2.5.4indirect
npm@biomejs/cli-darwin-arm642.5.4indirect
npm@biomejs/cli-darwin-x642.5.4indirect
npm@biomejs/cli-linux-arm642.5.4indirect
npm@biomejs/cli-linux-arm64-musl2.5.4indirect
npm@biomejs/cli-linux-x642.5.4indirect
npm@biomejs/cli-linux-x64-musl2.5.4indirect
npm@biomejs/cli-win32-arm642.5.4indirect
npm@biomejs/cli-win32-x642.5.4indirect
npm@hono/node-server1.19.17indirect
npm@kurkle/color0.3.4indirect
npm@playwright/test1.61.1indirect
npmaccepts2.0.0indirect
npmajv8.20.0indirect
npmajv-formats3.0.1indirect
npmbody-parser2.3.0indirect
npmbundle-name4.1.0indirect
npmbytes3.1.2indirect
npmcall-bind-apply-helpers1.0.2indirect
npmcall-bound1.0.4indirect
npmchart.js4.5.1indirect
npmcontent-disposition1.0.1indirect
npmcontent-type1.0.5indirect
npmcontent-type2.1.0indirect
npmcookie0.7.2indirect
npmcookie-signature1.2.2indirect
npmcors2.8.6indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdefault-browser5.5.0indirect
npmdefault-browser-id5.0.1indirect
npmdefine-lazy-prop3.0.0indirect
npmdepd2.0.0indirect
npmdunder-proto1.0.1indirect
npmee-first1.1.1indirect
npmencodeurl2.0.0indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.2indirect
npmescape-html1.0.3indirect
npmetag1.8.1indirect
npmeventsource3.0.7indirect
npmeventsource-parser3.1.0indirect
npmexpress-rate-limit8.5.2indirect
npmfast-deep-equal3.1.3indirect
npmfast-uri3.1.5indirect
npmfinalhandler2.1.1indirect
npmforwarded0.2.0indirect
npmfresh2.0.0indirect
npmfsevents2.3.2indirect
npmfunction-bind1.1.2indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmgopd1.2.0indirect
npmhas-symbols1.1.0indirect
npmhasown2.0.4indirect
npmhono4.13.2indirect
npmhttp-errors2.0.1indirect
npmiconv-lite0.7.2indirect
npminherits2.0.4indirect
npmip-address10.5.0indirect
npmipaddr.js1.9.1indirect
npmis-docker3.0.0indirect
npmis-in-ssh1.0.0indirect
npmis-inside-container1.0.0indirect
npmis-promise4.0.0indirect
npmis-wsl3.1.1indirect
npmisexe2.0.0indirect
npmjose6.2.3indirect
npmjson-schema-traverse1.0.0indirect
npmjson-schema-typed8.0.2indirect
npmmath-intrinsics1.1.0indirect
npmmedia-typer1.1.0indirect
npmmerge-descriptors2.0.0indirect
npmmime-db1.54.0indirect
npmmime-types3.0.2indirect
npmms2.1.3indirect
npmnegotiator1.0.0indirect
npmobject-assign4.1.1indirect
npmobject-inspect1.13.4indirect
npmon-finished2.4.1indirect
npmonce1.4.0indirect
npmparseurl1.3.3indirect
npmpath-key3.1.1indirect
npmpath-to-regexp8.4.2indirect
npmpkce-challenge5.0.1indirect
npmplaywright1.61.1indirect
npmplaywright-core1.61.1indirect
npmpowershell-utils0.1.0indirect
npmproxy-addr2.0.7indirect
npmqs6.15.3indirect
npmrange-parser1.2.1indirect
npmraw-body3.0.2indirect
npmrequire-from-string2.0.2indirect
npmrouter2.2.0indirect
npmrun-applescript7.1.0indirect
npmsafer-buffer2.1.2indirect
npmsend1.2.1indirect
npmserve-static2.2.1indirect
npmsetprototypeof1.2.0indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmside-channel1.1.1indirect
npmside-channel-list1.0.1indirect
npmside-channel-map1.0.1indirect
npmside-channel-weakmap1.0.2indirect
npmstatuses2.0.2indirect
npmtoidentifier1.0.1indirect
npmtype-is2.1.0indirect
npmunpipe1.0.0indirect
npmvary1.1.2indirect
npmwhich2.0.2indirect
npmwrappy1.0.2indirect
npmwsl-utils0.3.1indirect
npmzod4.4.3indirect
npmzod-to-json-schema3.25.2indirect
Dependency advisories 0

Installing npm:codelens-ai@0.10.3 pulls in 109 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.