Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-26 10:28 UTC

benquemax / brainpick

TypeScript · PythonMIT★ 3 stars⑂ 1 forksince Jul 2026View on GitHub ↗
KindCommand-line toolMCP serverNetwork serviceDesktop applicationLibraryWeb interfacehow this is determined

benquemax/brainpick holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (76/100) and lowest on Security (26/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

benquemaxOrganization
0 followers6 public repossince Nov 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIbrainpick0.8.72,533240 days agoknowledge-graphokfmcpragagentsbrainpickllm

Metrics by category

Vitality

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

67Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
6.9/36Commit cadence — 10/52 weeks with commits
18/18Commit volume — 179 commits in the last year
0/10OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year179
human_commit_share1
days_since_last_push0
active_weeks_last_year10
How it's scored
27/27Ships releases — 1 releases published
36/36Release recency — latest release 76 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count1
latest_release_tagdesktop-v0.1.0
releases_from_tagsno
days_since_latest_release76
mean_days_between_releases—

Community & Adoption

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

34At Risk · 17% of overall
How it's scored
4.9/60Stars — 3 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars3
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
45.4/80Monthly downloads — 2,533 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesbrainpick
dependents—
ecosystemspypi
total_downloads—
monthly_downloads2,533
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?

48Weak · 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 — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
16.8/42Issue resolution — 40% of issues closed
30/30PR acceptance — 1/1 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues3
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.4
closed_unmerged_prs0
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of benquemax
7.9/25Track record — 6 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginbenquemax
public_repos6
account_age_days310

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 0 days ago
20/20Version history — 24 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesbrainpick
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — packages/python/pyproject.toml ([tool.ruff])
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_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

55Moderate
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

26At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
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/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — project was created within the last 90 days. Please review its contents carefully
5/5Packaging — packaging workflow detected
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 53 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate2.6
Excluded from scoring (no data or not applicable): CI-Tests. 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.

76Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 87 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.87
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes10,751
How it's scored
12.6/18One-command bootstrap — packages/desktop/app/src-tauri/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — packages/python/pyproject.toml ([tool.ruff])
11/11Static type checking — packages/desktop/app/tsconfig.json, packages/desktop/tsconfig.json, packages/node/tsconfig.json, packages/webui/e2e/tsconfig.json, packages/webui/tsconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 30 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, package-lock.json, uv.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configspackages/desktop/app/tsconfig.json, packages/desktop/tsconfig.json, packages/node/tsconfig.json, packages/webui/e2e/tsconfig.json, packages/webui/tsconfig.json
agent_commit_share0.3
toolchain_manifestspackages/desktop/app/src-tauri/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.6/55Manageable file sizes — 3/387 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes77,243
source_files_sampled387
oversized_source_files3
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

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

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'brainpick' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index pypi:brainpick@0.8.7; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 2.6 / 10
2.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-09-26 10:28 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
10Packagingpackaging workflow detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities53 existing vulnerabilities detected
Direct dependencies 38
RegistryPackageVersion constraintManifest
npmbrainpick^0.8.0packages/desktop/package.json
npmcommander^13.1.0packages/desktop/package.json
npmexpress^5.2.1packages/desktop/package.json
npmsmol-toml^1.3.1packages/desktop/package.json
npm@modelcontextprotocol/sdk^1.29.0packages/node/package.json
npmchokidar^4.0.3packages/node/package.json
npmcommander^13.1.0packages/node/package.json
npmexpress^5.2.1packages/node/package.json
npmsmol-toml^1.3.1packages/node/package.json
npmyaml^2.8.0packages/node/package.json
npmzod^3.25.76packages/node/package.json
PyPIPyYAML>=6packages/python/pyproject.toml
PyPItomli>=2packages/python/pyproject.toml
PyPImcp>=1.9,<2packages/python/pyproject.toml
PyPIstarlette>=0.40packages/python/pyproject.toml
PyPIuvicorn>=0.30packages/python/pyproject.toml
PyPIwatchfiles>=0.24packages/python/pyproject.toml
PyPIhttpx>=0.27packages/python/pyproject.toml
npm@react-three/drei^10.0.0packages/webui/package.json
npm@react-three/fiber^9.0.0packages/webui/package.json
npmcamera-controls^3.0.0packages/webui/package.json
npmd3-force^3.0.0packages/webui/package.json
npmmarkdown-it^14.3.0packages/webui/package.json
npmmarked^15.0.0packages/webui/package.json
npmprosemirror-commands^1.7.1packages/webui/package.json
npmprosemirror-gapcursor^1.4.1packages/webui/package.json
npmprosemirror-history^1.5.0packages/webui/package.json
npmprosemirror-inputrules^1.5.1packages/webui/package.json
npmprosemirror-keymap^1.2.3packages/webui/package.json
npmprosemirror-markdown^1.13.5packages/webui/package.json
npmprosemirror-model^1.25.10packages/webui/package.json
npmprosemirror-schema-list^1.5.1packages/webui/package.json
npmprosemirror-state^1.4.4packages/webui/package.json
npmprosemirror-view^1.42.0packages/webui/package.json
npmreact^19.0.0packages/webui/package.json
npmreact-dom^19.0.0packages/webui/package.json
npmthree^0.175.0packages/webui/package.json
npmzustand^5.0.0packages/webui/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

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 — PyPI.