Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-25 05:19 UTC

maksimkurb / keen-pbr

keen-pbr is a Policy Based Routing toolkit for Keenetic and OpenWRT routers / Инструменты для выборочной маршрутизации на роутерах Keenetic и OpenWRT

C++ · TypeScriptGPL-3.0★ 138 stars⑂ 9 forkssince Nov 2024View on GitHub ↗
KindWeb interfacehow this is determined

maksimkurb/keen-pbr holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (86/100) and lowest on Security (44/100). It was last updated 7 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

Maxim KurbatovPersonal account
15 followers149 public repossince Jan 2012OneCell.ai

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

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recency — last push 7 days ago
19.4/36Commit cadence — 28/52 weeks with commits
18/18Commit volume — 781 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year781
human_commit_share1
days_since_last_push7
active_weeks_last_year28
How it's scored
27/27Ships releases — 24 releases published
36/36Release recency — latest release 30 days ago
27/27Release cadence — a release every ~13.5 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count24
latest_release_tagv3.3.1
releases_from_tagsno
days_since_latest_release30
mean_days_between_releases13.5

Community & Adoption

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

60Moderate · 17% of overall
How it's scored
34.7/60Stars — 138 stars
7.5/25Forks — 9 forks
3.9/15Watchers — 6 watchers
Inputs used
forks9
stars138
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes

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
0.7/22.5Commit distribution — top contributor authored 97% of commits
5.4/13.5Contributor breadth — 4 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.967
How it's scored
38.5/42Issue resolution — 92% of issues closed
24.6/30PR acceptance — 105/128 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs105
open_issues1
closed_issues11
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.917
closed_unmerged_prs23
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
8.7/25Owner reach — 15 followers of maksimkurb
25/25Track record — 149 public repos, account ~14 yr old
Inputs used
followers15
owner_typeUser
is_verified—
owner_loginmaksimkurb
public_repos149
account_age_days5,362
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 13 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
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_configyes
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 site — https://keen-pbr.fyi
10/10Repository description
10/10Topics — 14 topics
0/10Wiki
Inputs used
topicsdnsmasq, entware, keenetic, keenetic-routers, opkg, pbr, policy-based-routing, routing, keen-pbr, keenetic-pbr, netcraze, openwrt, openwrt-feed, openwrt-package
has_wikino
homepagehttps://keen-pbr.fyi
docs_sitehttps://keen-pbr.fyi
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

44Weak · 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
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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 3 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
0/7.5Vulnerabilities — 94 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3
Excluded from scoring (no data or not applicable): CI-Tests, 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
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories13
affected_packages2
assessed_packages9
unassessed_packages36
affected_by_severitycritical 1, unknown 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 9 resolved dependencies against OSV. 36 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

81Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://keen-pbr.fyi/llms.txt)
40/40Legible commit history — 83 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://keen-pbr.fyi/llms.txt
legible_history_share0.83
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes5,080
How it's scored
18/18One-command bootstrap — Makefile, packages/keenetic/keen-pbr/Makefile, packages/openwrt/keen-pbr/Makefile
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — frontend/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
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
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile, packages/keenetic/keen-pbr/Makefile, packages/openwrt/keen-pbr/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configsfrontend/tsconfig.json
agent_commit_share0
toolchain_manifestsdocs/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C++ (statically typed)
54.3/55Manageable file sizes — 6/443 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes103,590
source_files_sampled443
oversized_source_files6
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — docs/openapi.yaml
0/20MCP server — not applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filesdocs/openapi.yaml
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

138GitHub stars
4contributors
781commits, last 12 months
7days since last push
24releases
1bus factor
1open issues
Go, npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 9 ⇿
0Stars
9Forks
16Releases

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.

0246810922024-112025-092026-07
Major 1Minor 0Patch 11

Each point covers 2 days.

OpenSSF Scorecard 3.0 / 10
3.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-09-25 05:19 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
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 3 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
0Vulnerabilities94 existing vulnerabilities detected
Direct dependencies 20
RegistryPackageVersion constraintManifest
npm@base-ui/react^1.2.0frontend/package.json
npm@fontsource-variable/noto-sans^5.2.10frontend/package.json
npm@tailwindcss/vite^4.1.17frontend/package.json
npm@tanstack/react-form^1.28.5frontend/package.json
npm@tanstack/react-query^5.90.21frontend/package.json
npm@tanstack/react-query-devtools^5.91.3frontend/package.json
npmclass-variance-authority^0.7.1frontend/package.json
npmclsx^2.1.1frontend/package.json
npmcmdk^1.1.1frontend/package.json
npmi18next^25.10.4frontend/package.json
npmlucide-react^0.577.0frontend/package.json
npmreact^19.2.0frontend/package.json
npmreact-dom^19.2.0frontend/package.json
npmreact-i18next^16.6.1frontend/package.json
npmshadcn^4.0.7frontend/package.json
npmsonner^2.0.7frontend/package.json
npmtailwind-merge^3.5.0frontend/package.json
npmtailwindcss^4.1.17frontend/package.json
npmtw-animate-css^1.4.0frontend/package.json
npmwouter^3.9.0frontend/package.json
All dependencies 45

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

RegistryPackageVersionRelation
npm@base-ui/react^1.2.0direct
npm@fontsource-variable/noto-sans^5.2.10direct
npm@tailwindcss/vite^4.1.17direct
npm@tanstack/react-form^1.28.5direct
npm@tanstack/react-query^5.90.21direct
npm@tanstack/react-query-devtools^5.91.3direct
npmclass-variance-authority^0.7.1direct
npmclsx^2.1.1direct
npmcmdk^1.1.1direct
npmi18next^25.10.4direct
npmlucide-react^0.577.0direct
npmreact^19.2.0direct
npmreact-dom^19.2.0direct
npmreact-i18next^16.6.1direct
npmshadcn^4.0.7direct
npmsonner^2.0.7direct
npmtailwind-merge^3.5.0direct
npmtailwindcss^4.1.17direct
npmtw-animate-css^1.4.0direct
npmwouter^3.9.0direct
Gogithub.com/coreos/go-iptables0.8.0indirect
Gogithub.com/imfing/hextrav0.12.1indirect
Gogithub.com/pelletier/go-toml/v22.2.3indirect
Gogithub.com/valyala/bytebufferpool1.0.0indirect
Gogithub.com/valyala/fasttemplate1.2.2indirect
Gogithub.com/vishvananda/netlink1.3.0indirect
Gogithub.com/vishvananda/netns0.0.4indirect
Gogolang.org/x/sys0.10.0indirect
npm@eslint/js^9.39.1indirect
npm@types/node^24.10.1indirect
npm@types/react^19.2.5indirect
npm@types/react-dom^19.2.3indirect
npm@vitejs/plugin-react^5.1.1indirect
npmajv^8.18.0indirect
npmeslint^9.39.1indirect
npmeslint-plugin-react-hooks^7.0.1indirect
npmeslint-plugin-react-refresh^0.4.24indirect
npmglobals^16.5.0indirect
npmorval8.6.2indirect
npmprettier^3.8.1indirect
npmprettier-plugin-tailwindcss^0.7.2indirect
npmtypescript~5.9.3indirect
npmtypescript-eslint^8.46.4indirect
npmvite^7.2.4indirect
npmvite-plugin-compression^0.5.1indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 9 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 0 are direct. 36 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
orval8.6.2indirectcritical128.22.0
golang.org/x/sys0.10.0indirectunknown10.44.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.

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.