Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-19 21:53 UTC

iMicknl / python-sagemcom-api

(Unofficial) Python wrapper to interact with SagemCom F@st routers via internal API's.

PythonMIT★ 138 stars⑂ 48 forkssince Apr 2020View on GitHub ↗

iMicknl/python-sagemcom-api holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Engineering Quality (86/100) and lowest on AI Readiness (35/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Mick VleeshouwerPersonal account
300 followers81 public repossince Feb 2012@AWS Startups

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
PyPIsagemcom_api1.5.02,657200 days agosagemcom

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
8.3/36Commit cadence12/52 weeks with commits
13.9/18Commit volume34 commits in the last year
10/10OpenSSF Scorecard: Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year34
human_commit_share
days_since_last_push0
active_weeks_last_year12
How it's scored
27/27Ships releases21 releases published
36/36Release recencylatest release 0 days ago
19.8/27Release cadencea release every ~85.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count21
latest_release_tagv1.5.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases85.7
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?

53Moderate · 17% of overall
How it's scored
34.7/60Stars138 stars
13.9/25Forks48 forks
3.3/15Watchers5 watchers
Inputs used
forks48
stars138
watchers5
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
How it's scored
45.7/80Monthly downloads2,657 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagessagemcom_api
dependents
ecosystemspypi
total_downloads
monthly_downloads2,657
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 factor1 contributor(s) cover half of all commits
6.6/22.5Commit distributiontop contributor authored 71% of commits
13.5/13.5Contributor breadth19 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled19
top_contributor_share0.706
How it's scored
35.7/42Issue resolution85% of issues closed
16.7/30PR acceptance259/465 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 3/10 approved changesets -- score normalized to 3
Inputs used
merged_prs259
open_issues6
closed_issues34
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.85
closed_unmerged_prs206
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
17.8/25Owner reach300 followers of iMicknl
25/25Track record81 public repos, account ~14 yr old
Inputs used
followers300
owner_typeUser
is_verified
owner_loginiMicknl
public_repos81
account_age_days5,273
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 history20 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessagemcom_api
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicssagemcom, python
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?

59Moderate · 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-Tests29 out of 29 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
2.2/7.5Code-ReviewFound 3/10 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 4 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, 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.

35Weak · 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
11/11Lint / format config
0/11Static type checking
10/10Reproducible environmentdevcontainer, lockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
1/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontaineryes
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/10 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes21,170
source_files_sampled10
oversized_source_files0

Key facts

138GitHub stars
19contributors
34commits, last 12 months
0days since last push
21releases
1bus factor
6open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 5.9 / 10
5.9aggregate

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 21:53 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-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 3/10 approved changesets -- score normalized to 3
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
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 3
RegistryPackageVersion constraintManifest
PyPIaiohttp>=3.7.3,<4.0.0pyproject.toml
PyPIpyhumps>=3.0.2,<4.0.0pyproject.toml
PyPIbackoff>=1.10.0,<3.0pyproject.toml
All dependencies 32

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

RegistryPackageVersionRelation
PyPIaiohttp3.14.1direct
PyPIbackoff2.2.1direct
PyPIpyhumps3.8.0direct
PyPIaiohappyeyeballs2.6.1indirect
PyPIaiosignal1.4.0indirect
PyPIast-serialize0.6.0indirect
PyPIattrs26.1.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.13.5indirect
PyPIfrozenlist1.8.0indirect
PyPIidna3.15indirect
PyPIiniconfig2.3.0indirect
PyPIlibrt0.13.0indirect
PyPImultidict6.7.1indirect
PyPImypy2.3.0indirect
PyPImypy-extensions1.1.0indirect
PyPIpackaging26.0indirect
PyPIpathspec1.0.4indirect
PyPIpluggy1.6.0indirect
PyPIprek0.4.5indirect
PyPIpropcache0.4.1indirect
PyPIpygments2.20.0indirect
PyPIpytest9.1.0indirect
PyPIpytest-aiohttp1.1.1indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-cov7.1.0indirect
PyPIruff0.15.17indirect
PyPIsagemcom-api1.2.1indirect
PyPItomli2.4.1indirect
PyPIty0.0.50indirect
PyPItyping-extensions4.15.0indirect
PyPIyarl1.23.0indirect
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.15.0 — full methodology · metrics wiki.

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