Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 20:03 UTC

mbridak / not1mm

Not1MM != N1MM, An amateur radio contest logger for Linux.

PythonGPL-3.0★ 208 stars⑂ 77 forkssince Feb 2023View on GitHub ↗
KindDesktop applicationCommand-line toolLibraryhow this is determined

mbridak/not1mm holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (95/100) and lowest on Security (47/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

77
overall / 100
Good

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.

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

Ownership

Michael BridakPersonal account
33 followers61 public repossince Mar 2019K6GTE HOIP 102910

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 publish
PyPInot1mm26.10.182,8465372 days ago

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
33.9/36Commit cadence — 49/52 weeks with commits
18/18Commit volume — 791 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year791
human_commit_share1
days_since_last_push1
active_weeks_last_year49
How it's scored
27/27Ships releases — 6 releases published
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~3.4 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count6
latest_release_tag26.10.18
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases3.4

Community & Adoption

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

68Good · 17% of overall
How it's scored
37.6/60Stars — 208 stars
15.7/25Forks — 77 forks
6.2/15Watchers — 14 watchers
Inputs used
forks77
stars208
watchers14
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
46.1/80Monthly downloads — 2,846 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesnot1mm
dependents—
ecosystemspypi
total_downloads—
monthly_downloads2,846
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.6/22.5Commit distribution — top contributor authored 88% of commits
13.5/13.5Contributor breadth — 36 contributors
10/10OpenSSF Scorecard: Contributors — project has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled36
top_contributor_share0.884
How it's scored
40.1/42Issue resolution — 95% of issues closed
28.4/30PR acceptance — 304/321 decided PRs merged
6.5/13Newcomer PR acceptance — 1/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs304
open_issues12
closed_issues251
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d2
issue_closed_ratio0.954
closed_unmerged_prs17
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
11/25Owner reach — 33 followers of mbridak
25/25Track record — 61 public repos, account ~7 yr old
Inputs used
followers33
owner_typeUser
is_verified—
owner_loginmbridak
public_repos61
account_age_days2,761
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 pypi
35/35Publish recency — latest publish 2 days ago
20/20Version history — 537 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesnot1mm
ecosystemspypi
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
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_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicsamateur-radio, contesting, hamradio, linux
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

47Weak · 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
2.5/2.5Contributors — project has 9 contributing companies or organizations
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
7.5/7.5Maintained — 30 commit(s) and 23 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
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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): CI-Tests, Packaging. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
10.2/25Indirect dependencies free of known advisories — 1 affected: certifi 2026.10.18 (high 7.4)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages23
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Matched the pypi:not1mm@26.10.18 runtime dependency closure — what installing the published package pulls in — 23 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.

49Weak · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
11.7/40Legible commit history — 22 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.22
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes437
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 5 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.05
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
51.5/55Manageable file sizes — 12/188 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes199,006
source_files_sampled188
oversized_source_files12

Key facts

208GitHub stars
36contributors
791commits, last 12 months
1days since last push
6releases
1bus factor
12open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 77 ⇿
0Stars
77Forks
5Releases

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.

0204060807632023-052025-012026-10
Major 0Minor 0Patch 4

Each point covers 4 days.

OpenSSF Scorecard 3.8 / 10
3.8aggregate

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-10-21 20:02 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
10Contributorsproject has 9 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 23 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
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
PyPIPyQt6—pyproject.toml
PyPIrequests—pyproject.toml
PyPIdicttoxml—pyproject.toml
PyPIxmltodict—pyproject.toml
PyPIpyserial—pyproject.toml
PyPIsounddevice—pyproject.toml
PyPIsoundfile—pyproject.toml
PyPInumpy—pyproject.toml
PyPInotctyparser>= 23.6.21pyproject.toml
PyPIrapidfuzz—pyproject.toml
PyPIappdata—pyproject.toml
PyPIadif-io—pyproject.toml
PyPIpyobjc-framework-Cocoa—pyproject.toml
All dependencies 16

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

RegistryPackageVersionRelation
PyPIadif-io—direct
PyPIappdata—direct
PyPIdicttoxml—direct
PyPInotctyparser—direct
PyPInumpy—direct
PyPIpyobjc-framework-cocoa—direct
PyPIpyqt6—direct
PyPIpyserial—direct
PyPIrapidfuzz—direct
PyPIrequests—direct
PyPIsounddevice—direct
PyPIsoundfile—direct
PyPIxmltodict—direct
PyPIbuild—indirect
PyPIlevenshtein—indirect
PyPIsetuptools—indirect
Dependency advisories 1

Installing pypi:not1mm@26.10.18 pulls in 23 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
certifi2026.10.18indirecthigh22026.10.19

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