Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-17 10:23 UTC

wonderalexandre / mmcfilters

Header-only C++/Python framework for dynamic morphological trees, supporting incremental attribute computation and attribute-based filtering.

Jupyter Notebook · C++GPL-3.0★ 1 star⑂ 0 forkssince Aug 2026View on GitHub ↗

wonderalexandre/mmcfilters holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Vitality (74/100) and lowest on Community & Adoption (33/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

35 followers19 public repossince Nov 2015PPGI-UNINOVE

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
PyPImmcfilters4.1.03,348120 days agomorphological-treesmathematical-morphologyimage-processingcomputer-vision

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
9/36Commit cadence13/52 weeks with commits
18/18Commit volume142 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year142
human_commit_share1
days_since_last_push0
active_weeks_last_year13
How it's scored
27/27Ships releases2 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~0.5 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count2
latest_release_tagv4.1.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases0.5

Community & Adoption

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

33At Risk · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars1
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (GPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
47/80Monthly downloads3,348 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmmcfilters
dependents
ecosystemspypi
total_downloads
monthly_downloads3,348
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?

49Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.2/22.5Commit distributiontop contributor authored 95% of commits
2.7/13.5Contributor breadth2 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.948
How it's scored
0/42Issue resolution0% of issues closed
30/30PR acceptance1/1 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues1
closed_issues0
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0
closed_unmerged_prs0
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
11.2/25Owner reach35 followers of wonderalexandre
21.5/25Track record19 public repos, account ~10 yr old
Inputs used
followers35
owner_typeUser
is_verified
owner_loginwonderalexandre
public_repos19
account_age_days3,937
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 0 days ago
20/20Version history12 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmmcfilters
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 workflows4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests1 out of 1 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
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
0/5Packagingno data
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-ReleasesProject has not signed or included provenance with any releases.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4
Excluded from scoring (no data or not applicable): Packaging. 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.

37Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
18.1/40Legible commit history34 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.34
agent_instruction_files
agent_instruction_max_bytes
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 agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
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_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJupyter Notebook without a type-check config
52.2/55Manageable file sizes11/216 source files over 60KB
Inputs used
primary_languageJupyter Notebook
largest_source_bytes284,733
source_files_sampled216
oversized_source_files11
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

1GitHub stars
2contributors
142commits, last 12 months
0days since last push
2releases
1bus factor
1open issues
PyPIpackage 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
  • deps.dev does not index pypi:mmcfilters@4.1.0; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-08-17 10:22 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests1 out of 1 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
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
n/aPackagingpackaging workflow not 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
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPInumpy>=1.23pyproject.toml
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.31.0 — full methodology · metrics wiki.

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