Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 01:07 UTC

maximiliysiss / konfigo

Real-time centralized configuration management platform with typed schemas, versioned configuration, live updates, and multi-language SDK support

C# · SvelteMIT★ 1 star⑂ 0 forkssince May 2026View on GitHub ↗
KindLibraryNetwork servicehow this is determined

maximiliysiss/konfigo holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Engineering Quality (77/100) and lowest on Community & Adoption (25/100). It was last updated 37 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Maxim ZiminPersonal account
4 followers22 public repossince Apr 2017FInom

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
Gogithub.com/maximiliysiss/konfigov0.0.7-737 days ago
PyPIkonfigo0.0.739337 days agoconfigurationgrpckonfigorealtime-configsdk

Metrics by category

Vitality

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

69Good · 21% of overall
How it's scored
18/36Push recencylast push 37 days ago
4.2/36Commit cadence6/52 weeks with commits
16.3/18Commit volume65 commits in the last year
10/10OpenSSF Scorecard: Maintained19 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year65
human_commit_share1
days_since_last_push37
active_weeks_last_year6

Release discipline

100Exceptional
How it's scored
27/27Ships releases7 releases published
36/36Release recencylatest release 37 days ago
27/27Release cadencea release every ~8.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count7
latest_release_tagv0.0.7
releases_from_tagsno
days_since_latest_release37
mean_days_between_releases8.6
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?

25At Risk · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars1
watchers0
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_badges7
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
21.4/80Monthly downloads39 downloads/month across go, pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesgithub.com/maximiliysiss/konfigo, konfigo
dependents
ecosystemsgo, pypi
total_downloads
monthly_downloads39
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?

36Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution0% of issues closed
0/30PR acceptanceno decided pull requests or no data
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues1
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
5/25Owner reach4 followers of maximiliysiss
21.9/25Track record22 public repos, account ~9 yr old
Inputs used
followers4
owner_typeUser
is_verified
owner_loginmaximiliysiss
public_repos22
account_age_days3,431
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on go, pypi
35/35Publish recencylatest publish 37 days ago
20/20Version history7 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/maximiliysiss/konfigo, konfigo
ecosystemsgo, pypi
any_deprecatedno
min_days_since_publish37

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://github.com/maximiliysiss/konfigo/tree/master/packages/python
10/10Repository description
10/10Topics6 topics
0/10Wiki
Inputs used
topicsconfig-management, configuration, configuration-management, configuration-management-platform, feature-flags, real-time
has_wikino
homepage
docs_sitehttps://github.com/maximiliysiss/konfigo/tree/master/packages/python
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

36Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
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
7.5/7.5Maintained19 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities32 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): CI-Tests, 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.

50Moderate · 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 history0 of 65 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapapps/backend/src/Konfigo.Application/Konfigo.Application.csproj, apps/backend/src/Konfigo.Domain/Konfigo.Domain.csproj, apps/backend/src/Konfigo.Infrastructure/Konfigo.Infrastructure.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingapps/frontend/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 65
0/8Automated maintenanceno automated dependency updates observed
1/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, package-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsapps/frontend/tsconfig.json
agent_commit_share0
toolchain_manifestsapps/backend/src/Konfigo.Application/Konfigo.Application.csproj, apps/backend/src/Konfigo.Domain/Konfigo.Domain.csproj, apps/backend/src/Konfigo.Infrastructure/Konfigo.Infrastructure.csproj, apps/backend/src/Konfigo/Konfigo.csproj, apps/backend/tests/Konfigo.IntegrationTests/Konfigo.IntegrationTests.csproj, apps/backend/tests/Konfigo.UnitTests/Konfigo.UnitTests.csproj, packages/dotnet/src/Konfigo.Abstraction/Konfigo.Abstraction.csproj, packages/dotnet/src/Konfigo.Client/Konfigo.Client.csproj, packages/dotnet/tests/Konfigo.Client.IntegrationTests/Konfigo.Client.IntegrationTests.csproj, packages/dotnet/tests/Konfigo.Client.UnitTests/Konfigo.Client.UnitTests.csproj, packages/go/go.mod, samples/dotnet/src/Konfigo.Sample/Konfigo.Sample.csproj, samples/go/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/307 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes33,285
source_files_sampled307
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)apps/backend/src/Konfigo/protos/service.proto, packages/dotnet/src/Konfigo.Client/protos/service.proto, packages/go/protos/service.proto, packages/python/protos/service.proto
0/20MCP server
40/40Runnable examplessamples
Inputs used
example_dirssamples
has_mcp_signalno
api_schema_filesapps/backend/src/Konfigo/protos/service.proto, packages/dotnet/src/Konfigo.Client/protos/service.proto, packages/go/protos/service.proto, packages/python/protos/service.proto
interfaces_expected_ofnetwork-service

Key facts

1GitHub stars
1contributors
65commits, last 12 months
37days since last push
7releases
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

More detail

OpenSSF Scorecard 3.6 / 10
3.6aggregate

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-20 01:07 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
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
10Maintained19 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities32 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npm@microsoft/signalr^10.0.0apps/frontend/package.json
Gogoogle.golang.org/grpcv1.81.1packages/go/go.mod
Gogoogle.golang.org/protobufv1.36.11packages/go/go.mod
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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsGo, PyPI.