Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 01:56 UTC

duckcode-ai-labs / zlens

Ask your data. Get answers your team has verified. Open-source analytics workbench where every answer is labelled Certified, From Metrics or Needs review. Works on your dbt project or straight on your database, with lineage, Apps and an MCP server for Claude, Codex and Cursor.

TypeScriptApache-2.0★ 2 stars⑂ 0 forkssince Mar 2026View on GitHub ↗
KindMCP serverDesktop applicationWeb interfaceCommand-line toolLibraryhow this is determined

duckcode-ai-labs/zlens holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on Community & Adoption (50/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

duckcode-ai-labsOrganization
0 followers7 public repossince Oct 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@zlens/cli0.3.02,3471510 days ago—
npm@zlens/dql-lsp0.3.02,1991510 days ago—
npm@zlens/mcp0.3.02,6011510 days ago—
npm@zlens/core0.3.03,6001510 days agodqldashboardquerylanguagelexerparserast
npm@zlens/agent0.3.02,8991510 days ago—
npm@zlens/charts0.3.02,1961510 days ago—
npm@zlens/project0.3.03,0861510 days ago—

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
22.2/36Commit cadence — 32/52 weeks with commits
18/18Commit volume — 1,547 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,547
human_commit_share1
days_since_last_push0
active_weeks_last_year32

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 16 releases published
36/36Release recency — latest release 10 days ago
27/27Release cadence — a release every ~1.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count16
latest_release_tagzlens-v0.3.0
releases_from_tagsno
days_since_latest_release10
mean_days_between_releases1.6
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?

50Moderate · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars2
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 (Apache-2.0)
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
57/80Monthly downloads — 18,928 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@zlens/cli, @zlens/dql-lsp, @zlens/mcp, @zlens/core, @zlens/agent, @zlens/charts, @zlens/project
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads18,928
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.3/22.5Commit distribution — top contributor authored 76% of commits
2.7/13.5Contributor breadth — 2 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.764
How it's scored
42/42Issue resolution — 100% of issues closed
29.2/30PR acceptance — 349/359 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs349
open_issues0
closed_issues1
prs_merged_7d54
prs_decided_7d54
prs_merged_30d60
prs_decided_30d60
issue_closed_ratio1
closed_unmerged_prs10
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
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of duckcode-ai-labs
6.8/25Track record — 7 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginduckcode-ai-labs
public_repos7
account_age_days44

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 7 package(s) on npm
35/35Publish recency — latest publish 10 days ago
20/20Version history — 15 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@zlens/cli, @zlens/dql-lsp, @zlens/mcp, @zlens/core, @zlens/agent, @zlens/charts, @zlens/project
ecosystemsnpm
any_deprecatedno
min_days_since_publish10

Engineering Quality

Are baseline engineering and documentation practices in place?

81Excellent · 19% of overall
How it's scored
24/24CI workflows — 11 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
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://zlens.app
10/10Repository description
10/10Topics — 13 topics
10/10Wiki
Inputs used
topicsagentic, agentic-ai, analytics, analytics-engineering, dbt, duckdb, snowflake, certified-analytics, business-intelligence, data-lineage, mcp, semantic-layer, text-to-sql
has_wikiyes
homepagehttps://zlens.app
docs_sitehttps://zlens.app
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

55Moderate · 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 — 30 out of 30 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/30 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
4.5/5SAST — SAST tool detected but not run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 89 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: nodemailer 6.10.1 (high 7.5)
8.4/25Indirect dependencies free of known advisories — 2 affected: uuid 8.3.2 (high 7.5), zod 3.25.76 (high 7.5)
29.1/40No advisories left outstanding — 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 405 days ago
Inputs used
sourceosv
advisories24
affected_packages3
assessed_packages180
unassessed_packages0
affected_by_severityhigh 3
direct_affected_packages1
Matched the npm:@zlens/cli@0.3.0 runtime dependency closure — what installing the published package pulls in — 180 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.

74Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 100 of 100 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
agent_instruction_max_bytes3,503
How it's scored
12.6/18One-command bootstrap — apps/desktop/src-tauri/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — apps/cli/tsconfig.json, apps/dql-notebook/tsconfig.json, apps/vscode-extension/tsconfig.json, packages/datalex-lsp/tsconfig.json, packages/dql-agent/tsconfig.json, packages/dql-charts/tsconfig.json, packages/dql-compiler/tsconfig.json, packages/dql-connectors/tsconfig.json, packages/dql-core/tsconfig.json, packages/dql-governance/tsconfig.json, packages/dql-lsp/tsconfig.json, packages/dql-mcp/tsconfig.json, packages/dql-notebook/tsconfig.json, packages/dql-openlineage/tsconfig.json, packages/dql-plugin-api/tsconfig.json, packages/dql-project/tsconfig.json, packages/dql-runtime/tsconfig.json, packages/dql-slack/tsconfig.json, packages/dql-telemetry/tsconfig.json, packages/dql-ui/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 100 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 — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json, pnpm-lock.yaml
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configsapps/cli/tsconfig.json, apps/dql-notebook/tsconfig.json, apps/vscode-extension/tsconfig.json, packages/datalex-lsp/tsconfig.json, packages/dql-agent/tsconfig.json, packages/dql-charts/tsconfig.json, packages/dql-compiler/tsconfig.json, packages/dql-connectors/tsconfig.json, packages/dql-core/tsconfig.json, packages/dql-governance/tsconfig.json, packages/dql-lsp/tsconfig.json, packages/dql-mcp/tsconfig.json, packages/dql-notebook/tsconfig.json, packages/dql-openlineage/tsconfig.json, packages/dql-plugin-api/tsconfig.json, packages/dql-project/tsconfig.json, packages/dql-runtime/tsconfig.json, packages/dql-slack/tsconfig.json, packages/dql-telemetry/tsconfig.json, packages/dql-ui/tsconfig.json
agent_commit_share1
toolchain_manifestsapps/desktop/src-tauri/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
53.3/55Manageable file sizes — 68/2,229 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes2,813,858
source_files_sampled2,229
oversized_source_files68
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
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

2GitHub stars
2contributors
1,547commits, last 12 months
0days since last push
16releases
1bus factor
0open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package '@zlens/datalex-lsp' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 5.6 / 10
5.6aggregate

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-11-17 01:56 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-Tests30 out of 30 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/30 approved changesets -- score normalized to 0
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
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities89 existing vulnerabilities detected
Direct dependencies 81
RegistryPackageVersion constraintManifest
npm@zlens/cliworkspace:*package.json
npm@anthropic-ai/sdk^0.104.2apps/cli/package.json
npm@zlens/agentworkspace:*apps/cli/package.json
npm@zlens/dql-compilerworkspace:*apps/cli/package.json
npm@zlens/connectorsworkspace:*apps/cli/package.json
npm@zlens/coreworkspace:*apps/cli/package.json
npm@zlens/governanceworkspace:*apps/cli/package.json
npm@zlens/mcpworkspace:*apps/cli/package.json
npm@zlens/notebookworkspace:*apps/cli/package.json
npm@zlens/projectworkspace:*apps/cli/package.json
npm@zlens/slackworkspace:*apps/cli/package.json
npmbetter-sqlite3^12.11.1apps/cli/package.json
npmisomorphic-git~1.44.14apps/cli/package.json
npmjs-yaml^4.3.2apps/cli/package.json
npmnode-cron^3.0.3apps/cli/package.json
npmnodemailer^10.4.0apps/cli/package.json
npmopenai^6.44.0apps/cli/package.json
npmtar-stream^2.2.0apps/cli/package.json
npm@zlens/notebook-appworkspace:*apps/desktop/package.json
npm@codemirror/autocomplete^6.20.1apps/dql-notebook/package.json
npm@codemirror/commands^6.7.1apps/dql-notebook/package.json
npm@codemirror/lang-sql^6.8.0apps/dql-notebook/package.json
npm@codemirror/language^6.10.8apps/dql-notebook/package.json
npm@codemirror/search^6.6.0apps/dql-notebook/package.json
npm@codemirror/state^6.5.2apps/dql-notebook/package.json
npm@codemirror/theme-one-dark^6.1.2apps/dql-notebook/package.json
npm@codemirror/view^6.36.3apps/dql-notebook/package.json
npm@dagrejs/dagre^3.0.0apps/dql-notebook/package.json
npm@zlens/coreworkspace:*apps/dql-notebook/package.json
npm@zlens/uiworkspace:*apps/dql-notebook/package.json
npm@lezer/highlight^1.2.3apps/dql-notebook/package.json
npm@radix-ui/react-dialog^1.1.6apps/dql-notebook/package.json
npm@tanstack/react-query^5apps/dql-notebook/package.json
npm@xyflow/react^12.10.1apps/dql-notebook/package.json
npmecharts6.1.0apps/dql-notebook/package.json
npmlucide-react^0.563.0apps/dql-notebook/package.json
npmreact^18.3.0apps/dql-notebook/package.json
npmreact-dom^18.3.0apps/dql-notebook/package.json
npmsql-formatter^15.7.2apps/dql-notebook/package.json
npmtailwindcss^4.0.0apps/dql-notebook/package.json
npmzustand^5.0.0apps/dql-notebook/package.json
npm@zlens/cliworkspace:*packages/create-zlens/package.json
npmajv^8.12.0packages/datalex-lsp/package.json
npmjs-yaml^4.3.2packages/datalex-lsp/package.json
npmvscode-languageserver^9.0.1packages/datalex-lsp/package.json
npmvscode-languageserver-textdocument^1.0.11packages/datalex-lsp/package.json
npm@zlens/coreworkspace:*packages/dql-agent/package.json
npm@zlens/governanceworkspace:*packages/dql-agent/package.json
npm@zlens/projectworkspace:*packages/dql-agent/package.json
npmbetter-sqlite3^12.11.1packages/dql-agent/package.json
npmjs-yaml^4.3.2packages/dql-agent/package.json
npm@visx/axis^3.10.0packages/dql-charts/package.json
npm@visx/grid^3.5.0packages/dql-charts/package.json
npm@visx/group^3.3.0packages/dql-charts/package.json
npm@visx/scale^3.5.0packages/dql-charts/package.json
npm@visx/shape^3.5.0packages/dql-charts/package.json
npm@visx/tooltip^3.3.0packages/dql-charts/package.json
npm@visx/responsive^3.10.0packages/dql-charts/package.json
npm@visx/gradient^3.3.0packages/dql-charts/package.json
npm@visx/legend^3.10.0packages/dql-charts/package.json
npm@visx/text^3.3.0packages/dql-charts/package.json
npm@visx/curve^3.3.0packages/dql-charts/package.json
npm@zlens/coreworkspace:*packages/dql-compiler/package.json
npmjs-yaml^4.3.2packages/dql-core/package.json
npmnode-sql-parser^5.4.0packages/dql-core/package.json
npmyaml^2.8.2packages/dql-core/package.json
npm@zlens/coreworkspace:*packages/dql-governance/package.json
npm@zlens/projectworkspace:*packages/dql-governance/package.json
npmvscode-languageserver^9.0.1packages/dql-lsp/package.json
npmvscode-languageserver-textdocument^1.0.11packages/dql-lsp/package.json
npm@zlens/coreworkspace:*packages/dql-lsp/package.json
npm@zlens/agentworkspace:*packages/dql-mcp/package.json
npm@zlens/coreworkspace:*packages/dql-mcp/package.json
npm@zlens/governanceworkspace:*packages/dql-mcp/package.json
npm@zlens/projectworkspace:*packages/dql-mcp/package.json
npm@modelcontextprotocol/sdk^1.32.2packages/dql-mcp/package.json
npmzod^4.6.6packages/dql-mcp/package.json
npm@zlens/coreworkspace:*packages/dql-notebook/package.json
npm@zlens/connectorsworkspace:*packages/dql-notebook/package.json
npm@zlens/coreworkspace:*packages/dql-project/package.json
npmbetter-sqlite3^12.11.1packages/dql-project/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 3

Installing npm:@zlens/cli@0.3.0 pulls in 180 packages, direct and transitive: 3 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
nodemailer6.10.1directhigh2210.1.4
uuid8.3.2indirecthigh113.0.1
zod3.25.76indirecthigh14.6.6

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.