Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-19 01:13 UTC

tr4nt0r / pythonkuma

Simple Python wrapper for Uptime Kuma

PythonMIT★ 2 stars⑂ 2 forkssince Jun 2025View on GitHub ↗

tr4nt0r/pythonkuma holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (88/100) and lowest on Community & Adoption (42/100). It was last updated 2 days 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

ManuPersonal account
32 followers56 public repossince May 2013

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
PyPIpythonkuma0.5.313,4101967 days ago

Metrics by category

Vitality

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

88Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
28.4/36Commit cadence — 41/52 weeks with commits
18/18Commit volume — 186 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year186
human_commit_share0.15
days_since_last_push2
active_weeks_last_year41
How it's scored
27/27Ships releases — 11 releases published
36/36Release recency — latest release 67 days ago
19.8/27Release cadence — a release every ~50.8 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count11
latest_release_tagv0.5.3
releases_from_tagsno
days_since_latest_release67
mean_days_between_releases50.8

Community & Adoption

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

42Weak · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 2 forks
0/15Watchers — 1 watchers
Inputs used
forks2
stars2
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/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_conductno
readme_badge_servicesbadge.fury.io, codecov.io, github.com, shields.io
has_pull_request_templateno
How it's scored
55/80Monthly downloads — 13,410 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespythonkuma
dependents—
ecosystemspypi
total_downloads—
monthly_downloads13,410
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
2/22.5Commit distribution — top contributor authored 91% of commits
2.7/13.5Contributor breadth — 2 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.913
How it's scored
0/42Issue resolution — 0% of issues closed
27.8/30PR acceptance — 270/291 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs270
open_issues1
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0
closed_unmerged_prs21
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Code-Review. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
10.9/25Owner reach — 32 followers of tr4nt0r
24.8/25Track record — 56 public repos, account ~13 yr old
Inputs used
followers32
owner_typeUser
is_verified—
owner_logintr4nt0r
public_repos56
account_age_days4,934
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 67 days ago
20/20Version history — 19 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespythonkuma
ecosystemspypi
any_deprecatedno
min_days_since_publish67

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://tr4nt0r.github.io/pythonkuma/
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://tr4nt0r.github.io/pythonkuma/
docs_sitehttps://tr4nt0r.github.io/pythonkuma/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

68Good · 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
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — no data
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
5/5SAST — SAST tool is run on all commits
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_aggregate6
Excluded from scoring (no data or not applicable): Code-Review, Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages12
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:pythonkuma@0.5.3 runtime dependency closure — what installing the published package pulls in — 12 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.

44Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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 — pyproject.toml ([tool.ruff])
11/11Static type checking — pythonkuma/py.typed
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 85 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configspythonkuma/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.85
How it's scored
27/45Type-checkable code — Python with type-check config (pythonkuma/py.typed)
55/55Manageable file sizes — 0/8 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes4,701
source_files_sampled8
oversized_source_files0

Key facts

2GitHub stars
2contributors
186commits, last 12 months
2days since last push
11releases
1bus factor
1open 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 ★ / 2 ⇿
0Stars
2Forks
2Releases

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.

111222212026-052026-082026-11
Major 0Minor 0Patch 2
OpenSSF Scorecard 6.0 / 10
6.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-11-19 01:12 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
n/aCode-ReviewFound no human activity in the last 30 changesets
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
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 3
RegistryPackageVersion constraintManifest
PyPIaiohttp>=3.14.0pyproject.toml
PyPIprometheus-client>=0.21.0pyproject.toml
PyPImashumaro>=3.13.1pyproject.toml
All dependencies 5

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

RegistryPackageVersionRelation
PyPIaiohttp—direct
PyPIaiohttp3.11.0b0direct
PyPImashumaro—direct
PyPIprometheus-client—direct
PyPIprometheus-client0.22.1direct
Dependency advisories 0

Installing pypi:pythonkuma@0.5.3 pulls in 12 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.