Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-19 01:06 UTC

computational-cell-analytics / micro-sam

Segment Anything for Microscopy

Jupyter Notebook · PythonMIT★ 701 stars⑂ 105 forkssince May 2023View on GitHub ↗
KindLibraryDesktop applicationhow this is determined

computational-cell-analytics/micro-sam holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on AI Readiness (34/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

86 followers36 public repossince Jun 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPImicro_sam1.8.6-71 day 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 recencylast push 1 days ago
22.8/36Commit cadence33/52 weeks with commits
18/18Commit volume157 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year157
human_commit_share
days_since_last_push1
active_weeks_last_year33

Release discipline

100Exceptional
How it's scored
27/27Ships releases48 releases published
36/36Release recencylatest release 1 days ago
27/27Release cadencea release every ~15.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count48
latest_release_tagv1.8.6
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases15.5
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?

60Moderate · 17% of overall
How it's scored
46.2/60Stars701 stars
16.8/25Forks105 forks
5/15Watchers9 watchers
Inputs used
forks105
stars701
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

73Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9.1/22.5Commit distributiontop contributor authored 60% of commits
13.5/13.5Contributor breadth20 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled20
top_contributor_share0.597
How it's scored
36.4/42Issue resolution87% of issues closed
27.8/30PR acceptance827/892 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 13/27 approved changesets -- score normalized to 4
Inputs used
merged_prs827
open_issues52
closed_issues336
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.866
closed_unmerged_prs65
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
13.9/25Owner reach86 followers of computational-cell-analytics
19.7/25Track record36 public repos, account ~4 yr old
Inputs used
followers86
owner_typeOrganization
is_verified
owner_logincomputational-cell-analytics
public_repos36
account_age_days1,508
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 pypi
35/35Publish recencylatest publish 1 days ago
20/20Version history7 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmicro_sam
ecosystemspypi
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests27 out of 27 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://computational-cell-analytics.github.io/micro-sam/
10/10Repository description
10/10Topics9 topics
0/10Wiki
Inputs used
topicsmicroscopy-images, segment-anything, segmentation, cell-segmentation, napari, nuclei-segmentation, mitochondria-segmentation, micro-sam, bioimage-analysis
has_wikino
homepagehttps://computational-cell-analytics.github.io/micro-sam/
docs_sitehttps://computational-cell-analytics.github.io/micro-sam/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

53Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests27 out of 27 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 13/27 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 5 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. 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.

34At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJupyter Notebook without a type-check config
54.3/55Manageable file sizes3/247 source files over 60KB
Inputs used
primary_languageJupyter Notebook
largest_source_bytes87,623
source_files_sampled247
oversized_source_files3
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples, notebooks
Inputs used
example_dirsexamples, notebooks
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

701GitHub stars
20contributors
157commits, last 12 months
1days since last push
48releases
1bus factor
52open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 5.3 / 10
5.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-07-19 01:05 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-Tests27 out of 27 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 13/27 approved changesets -- score normalized to 4
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 30
RegistryPackageVersion constraintManifest
PyPIbioimage-cpp>=0.3setup.cfg
PyPIbioimageio.coresetup.cfg
PyPIh5pysetup.cfg
PyPIimagecodecssetup.cfg
PyPIimageiosetup.cfg
PyPIjoblibsetup.cfg
PyPIkorniasetup.cfg
PyPImagicguisetup.cfg
PyPImatplotlibsetup.cfg
PyPInapari>=0.7setup.cfg
PyPInatsortsetup.cfg
PyPInetworkxsetup.cfg
PyPInumpysetup.cfg
PyPIpandassetup.cfg
PyPIpoochsetup.cfg
PyPIPyQt6setup.cfg
PyPIpython-elf>=0.9setup.cfg
PyPIscikit-imagesetup.cfg
PyPIscikit-learnsetup.cfg
PyPIsegment-anythingsetup.cfg
PyPIsuperqtsetup.cfg
PyPItimmsetup.cfg
PyPItorch>=2.5setup.cfg
PyPItorch-em>=0.9setup.cfg
PyPItorchvisionsetup.cfg
PyPItqdmsetup.cfg
PyPItrackastra>=0.5.3setup.cfg
PyPIxarraysetup.cfg
PyPIxxhashsetup.cfg
PyPIzarrsetup.cfg
All dependencies 41

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

RegistryPackageVersionRelation
PyPIbioimage-cppdirect
PyPIbioimageio-coredirect
PyPIh5pydirect
PyPIimagecodecsdirect
PyPIimageiodirect
PyPIjoblibdirect
PyPIkorniadirect
PyPImagicguidirect
PyPImatplotlibdirect
PyPInaparidirect
PyPInatsortdirect
PyPInetworkxdirect
PyPInumpydirect
PyPIpandasdirect
PyPIpoochdirect
PyPIpyqt6direct
PyPIpython-elfdirect
PyPIscikit-imagedirect
PyPIscikit-learndirect
PyPIsegment-anythingdirect
PyPIsuperqtdirect
PyPItimmdirect
PyPItorchdirect
PyPItorch-emdirect
PyPItorchvisiondirect
PyPItqdmdirect
PyPItrackastradirect
PyPIxarraydirect
PyPIxxhashdirect
PyPIzarrdirect
PyPIbuildindirect
PyPIcoverageindirect
PyPIline-profilerindirect
PyPIpdocindirect
PyPIpytestindirect
PyPIpytest-covindirect
PyPIpytest-qtindirect
PyPIsetuptoolsindirect
PyPIsnakevizindirect
PyPItabulateindirect
PyPItwineindirect
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.14.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.