Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 10:16 UTC

kakyoism / kkpyutil

Building blocks for system administration and DevOps

PythonMIT★ 0 stars⑂ 1 forksince Jan 2021View on GitHub ↗

kakyoism/kkpyutil holds a health index of 35 out of 100, placing it in the Weak band. It scores highest on Vitality (53/100) and lowest on Community & Adoption (24/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

overall / 100

Weak

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.

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)

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

Ownership

kakyoismPersonal account

9 followers21 public repossince Nov 2010

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
PyPI	kkpyutil	1.57.2	-	382	2 days ago	utility logging systems

Metrics by category

Vitality

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

53Moderate · 21% of overall

Development activity

67Good

How it's scored

36/36	Push recency — last push 2 days ago
7.6/36	Commit cadence — 11/52 weeks with commits
13.4/18	Commit volume — 30 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	30
human_commit_share	1
days_since_last_push	2
active_weeks_last_year	11

Release discipline

32At Risk

How it's scored

16.2/27	Ships releases — 1 version tags (no GitHub releases)
0/36	Release recency — latest release 1,339 days ago
12.6/27	Release cadence — cadence unknown (single release)
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	1
latest_release_tag	v0.114.0
releases_from_tags	yes
days_since_latest_release	1,339
mean_days_between_releases	—

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?

24At Risk · 17% of overall

Popularity & adoption

1Critical

How it's scored

0/60	Stars — 0 stars
0/25	Forks — 1 forks
0/15	Watchers — 1 watchers

Inputs used

forks	1
stars	0
watchers	1
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	0
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Sustainability & Governance

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

36Weak · 23% of overall

Maintainer resilience (bus factor)

10Critical

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
0/22.5	Commit distribution — top contributor authored 100% of commits
1.4/13.5	Contributor breadth — 1 contributors
0/10	OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0

Inputs used

bus_factor	1
contributors_sampled	1
top_contributor_share	1

Issue & PR responsiveness

1Critical

How it's scored

0/42	Issue resolution — no issues or no data
0/30	PR acceptance — no decided pull requests or no data
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0

Inputs used

merged_prs	0
open_issues	0
closed_issues	0
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	—
closed_unmerged_prs	0
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

49Weak

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
7.2/25	Owner reach — 9 followers of kakyoism
21.8/25	Track record — 21 public repos, account ~15 yr old

Inputs used

followers	9
owner_type	User
is_verified	—
owner_login	kakyoism
public_repos	21
account_age_days	5,784

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on pypi
35/35	Publish recency — latest publish 2 days ago
20/20	Version history — 382 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	kkpyutil
ecosystems	pypi
any_deprecated	no
min_days_since_publish	2

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall

Engineering practices

30At Risk

How it's scored

0/24	CI workflows
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — no data

Inputs used

has_ci	no
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

65Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://github.com/kakyoism/kkpyutil/README.md
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	https://github.com/kakyoism/kkpyutil/README.md
has_readme	yes
has_docs_dir	no
has_description	yes

Security

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

47Weak · 16% of overall

Security posture

34At Risk

How it's scored

6.8/7.5	Binary-Artifacts — binaries present in source code
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
0/2.5	CI-Tests — no data
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/30 approved changesets -- score normalized to 0
0/2.5	Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10	Dangerous-Workflow — no data
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
7.5/7.5	Maintained — 15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
0/5	SAST — no SAST tool detected
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — no data
6/7.5	Vulnerabilities — 2 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	12
scorecard_version	v5.5.0
checks_inconclusive	6
scorecard_aggregate	3.4

Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	4
affected_packages	2
assessed_packages	10
unassessed_packages	0
affected_by_severity	moderate 1, low 1
direct_affected_packages	0

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 10 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

26At Risk · 4% of overall

Agent context & guidance

2Critical

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
1.6/40	Legible commit history — 3 of 100 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.03
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

36Weak

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
0/11	Static type checking
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	yes
lockfiles	poetry.lock
has_dockerfile	no
typed_language	no
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

48Weak

How it's scored

0/45	Type-checkable code — Python without a type-check config
48.1/55	Manageable file sizes — 2/16 source files over 60KB

Inputs used

primary_language	Python
largest_source_bytes	135,464
source_files_sampled	16
oversized_source_files	2

Key facts

0GitHub stars

1contributors

30commits, last 12 months

2days since last push

1releases

1bus factor

0open issues

PyPIpackage ecosystems

Data collection warnings

pypi download statistics for 'kkpyutil' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced

More detail

OpenSSF Scorecard 3.4 / 10

3.4aggregate

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-09-18 10:15 UTC

9	Binary-Artifacts	binaries present in source code
0	Branch-Protection	branch protection not enabled on development/release branches
n/a	CI-Tests	no pull request found
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 0/30 approved changesets -- score normalized to 0
0	Contributors	project has 0 contributing companies or organizations -- score normalized to 0
n/a	Dangerous-Workflow	no workflows found
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
0	SAST	no SAST tool detected
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
n/a	Token-Permissions	No tokens found
8	Vulnerabilities	2 existing vulnerabilities detected

All dependencies 10

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

Registry	Package	Version	Relation
PyPI	colorama	`0.4.6`	indirect
PyPI	coverage	`7.10.7`	indirect
PyPI	exceptiongroup	`1.3.1`	indirect
PyPI	iniconfig	`2.1.0`	indirect
PyPI	packaging	`25.0`	indirect
PyPI	pluggy	`1.6.0`	indirect
PyPI	pygments	`2.19.2`	indirect
PyPI	pytest	`8.4.2`	indirect
PyPI	tomli	`2.4.0`	indirect
PyPI	typing-extensions	`4.15.0`	indirect

Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 10 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 0 are direct.

Package	Version	Relation	Severity	Advisories	Fixed in
pytest	`8.4.2`	indirect	moderate	2	`9.0.3`
pygments	`2.19.2`	indirect	low	2	`2.20.0`

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.

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.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records