Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-08 20:10 UTC

ApiTreeCZ / toolbox

🧰 Shared configurations and utilities for @ApiTreeCZ projects

TypeScriptNo license detected★ 0 stars⑂ 0 forkssince Oct 2023View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

ApiTreeCZ/toolbox holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Engineering Quality (78/100) and lowest on Community & Adoption (33/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

ApiTree s.r.o.Organization · verified domain
10 followers8 public repossince Mar 2018

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

Metrics by category

Vitality

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

57Moderate · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 541 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_year541
human_commit_share0.07
days_since_last_push0
active_weeks_last_year43
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

33At Risk · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 2 watchers
Inputs used
forks0
stars0
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno
How it's scored
54.1/80Monthly downloads — 11,498 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@apitree.cz/cli, @apitree.cz/ts-utils, @apitree.cz/ts-config, @apitree.cz/eslint-config, @apitree.cz/vitest-config, @apitree.cz/typedoc-config, @apitree.cz/prettier-config, @apitree.cz/testing-library
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads11,498
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.5/22.5Commit distribution — top contributor authored 98% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.977
How it's scored
31.5/42Issue resolution — 75% of issues closed
23.3/30PR acceptance — 501/645 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs501
open_issues2
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.75
closed_unmerged_prs144
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, OpenSSF Scorecard: Code-Review. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
7.5/25Owner reach — 10 followers of ApiTreeCZ
18.9/25Track record — 8 public repos, account ~8 yr old
Inputs used
followers10
owner_typeOrganization
is_verifiedyes
owner_loginApiTreeCZ
public_repos8
account_age_days3,140

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 8 package(s) on npm
35/35Publish recency — latest publish 37 days ago
20/20Version history — 304 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@apitree.cz/cli, @apitree.cz/ts-utils, @apitree.cz/ts-config, @apitree.cz/eslint-config, @apitree.cz/vitest-config, @apitree.cz/typedoc-config, @apitree.cz/prettier-config, @apitree.cz/testing-library
ecosystemsnpm
any_deprecatedno
min_days_since_publish37

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
6.4/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_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 11 topics
10/10Wiki
Inputs used
topicseslint-config, esm, prettier-config, react-testing-library, tsconfig, vitest, typedoc, cli, utils, lint-staged-config, code-style
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

63Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all 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
0/2.5License — license file not 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
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.4
Excluded from scoring (no data or not applicable): Code-Review, Packaging, Signed-Releases. 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_packages33
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 npm:@apitree.cz/cli@1.0.3 runtime dependency closure — what installing the published package pulls in — 33 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.

73Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
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_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes3,384
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 — eslint.config.js
11/11Static type checking — packages/cli/tsconfig.json, packages/eslint-config-nestjs/tsconfig.json, packages/eslint-config-nextjs/tsconfig.json, packages/eslint-config-react/tsconfig.json, packages/eslint-config-storybook/tsconfig.json, packages/eslint-config/tsconfig.json, packages/lint-staged-config/tsconfig.json, packages/prettier-config/tsconfig.json, packages/testing-library/tests/tsconfig.json, packages/testing-library/tsconfig.json, packages/ts-config/tsconfig.json, packages/ts-utils/tsconfig.json, packages/typedoc-config/tsconfig.json, packages/vitest-config/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 92 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configspackages/cli/tsconfig.json, packages/eslint-config-nestjs/tsconfig.json, packages/eslint-config-nextjs/tsconfig.json, packages/eslint-config-react/tsconfig.json, packages/eslint-config-storybook/tsconfig.json, packages/eslint-config/tsconfig.json, packages/lint-staged-config/tsconfig.json, packages/prettier-config/tsconfig.json, packages/testing-library/tests/tsconfig.json, packages/testing-library/tsconfig.json, packages/ts-config/tsconfig.json, packages/ts-utils/tsconfig.json, packages/typedoc-config/tsconfig.json, packages/vitest-config/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.92
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/93 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes2,624
source_files_sampled93
oversized_source_files0

Key facts

0GitHub stars
3contributors
541commits, last 12 months
0days since last push
0releases
1bus factor
2open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 5.4 / 10
5.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-10-08 20:09 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all 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
0Licenselicense file not detected
10Maintained30 commit(s) and 0 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
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 42
RegistryPackageVersion constraintManifest
npm@apitree.cz/ts-utilsworkspace:*packages/cli/package.json
npm@commander-js/extra-typings^15.0.0packages/cli/package.json
npm@manypkg/find-root^3.1.0packages/cli/package.json
npm@manypkg/get-packages^3.1.0packages/cli/package.json
npmcommander^15.0.0packages/cli/package.json
npmdeepmerge^4.3.1packages/cli/package.json
npmexeca^10.0.1packages/cli/package.json
npmpath-exists^5.0.0packages/cli/package.json
npmts-toolbelt^9.6.0packages/cli/package.json
npmzod^4.5.4packages/cli/package.json
npm@next/eslint-plugin-next^16.3.4packages/eslint-config-nextjs/package.json
npm@vitest/eslint-plugin^1.6.27packages/eslint-config-react/package.json
npmeslint-config-prettier^10.1.8packages/eslint-config-react/package.json
npmeslint-plugin-formatjs^6.6.1packages/eslint-config-react/package.json
npmeslint-plugin-jest-dom^5.10.1packages/eslint-config-react/package.json
npmeslint-plugin-mdx^3.8.1packages/eslint-config-react/package.json
npmeslint-plugin-react^7.37.5packages/eslint-config-react/package.json
npmeslint-plugin-react-hooks^7.1.1packages/eslint-config-react/package.json
npmeslint-plugin-testing-library^7.16.2packages/eslint-config-react/package.json
npmglobals^17.11.0packages/eslint-config-react/package.json
npmeslint-plugin-storybook^10.5.10packages/eslint-config-storybook/package.json
npm@eslint/core^1.2.1packages/eslint-config/package.json
npm@eslint/eslintrc^3.3.6packages/eslint-config/package.json
npm@eslint/js^9.39.5packages/eslint-config/package.json
npm@typescript-eslint/parser^8.69.0packages/eslint-config/package.json
npm@vitest/eslint-plugin^1.6.27packages/eslint-config/package.json
npmeslint-config-prettier^10.1.8packages/eslint-config/package.json
npmeslint-import-resolver-typescript^4.4.5packages/eslint-config/package.json
npmeslint-plugin-import^2.32.0packages/eslint-config/package.json
npmeslint-plugin-unicorn^65.0.1packages/eslint-config/package.json
npmeslint-plugin-unused-imports^4.4.1packages/eslint-config/package.json
npmglobals^17.11.0packages/eslint-config/package.json
npmtypescript-eslint^8.69.0packages/eslint-config/package.json
npmprettier-plugin-packagejson^3.0.2packages/prettier-config/package.json
npm@testing-library/dom^10.4.1packages/testing-library/package.json
npm@testing-library/jest-dom^7.0.1packages/testing-library/package.json
npmjsdom^30.0.1packages/testing-library/package.json
npmtypedoc-plugin-markdown^4.13.0packages/typedoc-config/package.json
npm@swc/core^1.16.1packages/vitest-config/package.json
npm@vitejs/plugin-react^6.1.1packages/vitest-config/package.json
npmunplugin-swc^1.5.11packages/vitest-config/package.json
npmvite^8.2.2packages/vitest-config/package.json
All dependencies 67

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

RegistryPackageVersionRelation
npm@commander-js/extra-typings^15.0.0direct
npm@eslint/core^1.2.1direct
npm@eslint/eslintrc^3.3.6direct
npm@eslint/js^9.39.5direct
npm@manypkg/find-root^3.1.0direct
npm@manypkg/get-packages^3.1.0direct
npm@next/eslint-plugin-next^16.3.4direct
npm@swc/core^1.16.1direct
npm@testing-library/dom^10.4.1direct
npm@testing-library/jest-dom^7.0.1direct
npm@typescript-eslint/parser^8.69.0direct
npm@vitejs/plugin-react^6.1.1direct
npm@vitest/eslint-plugin^1.6.27direct
npmcommander^15.0.0direct
npmdeepmerge^4.3.1direct
npmeslint-config-prettier^10.1.8direct
npmeslint-import-resolver-typescript^4.4.5direct
npmeslint-plugin-formatjs^6.6.1direct
npmeslint-plugin-import^2.32.0direct
npmeslint-plugin-jest-dom^5.10.1direct
npmeslint-plugin-mdx^3.8.1direct
npmeslint-plugin-react^7.37.5direct
npmeslint-plugin-react-hooks^7.1.1direct
npmeslint-plugin-storybook^10.5.10direct
npmeslint-plugin-testing-library^7.16.2direct
npmeslint-plugin-unicorn^65.0.1direct
npmeslint-plugin-unused-imports^4.4.1direct
npmexeca^10.0.1direct
npmglobals^17.11.0direct
npmjsdom^30.0.1direct
npmpath-exists^5.0.0direct
npmprettier-plugin-packagejson^3.0.2direct
npmts-toolbelt^9.6.0direct
npmtypedoc-plugin-markdown^4.13.0direct
npmtypescript-eslint^8.69.0direct
npmunplugin-swc^1.5.11direct
npmvite^8.2.2direct
npmzod^4.5.4direct
npm@pnpm/exe.android-arm6412.10.1indirect
npm@pnpm/exe.android-x6412.10.1indirect
npm@pnpm/exe.darwin-arm6412.10.1indirect
npm@pnpm/exe.darwin-x6412.10.1indirect
npm@pnpm/exe.freebsd-x6412.10.1indirect
npm@pnpm/exe.linux-arm6412.10.1indirect
npm@pnpm/exe.linux-arm64-musl12.10.1indirect
npm@pnpm/exe.linux-ppc6412.10.1indirect
npm@pnpm/exe.linux-riscv6412.10.1indirect
npm@pnpm/exe.linux-s390x12.10.1indirect
npm@pnpm/exe.linux-x6412.10.1indirect
npm@pnpm/exe.linux-x64-musl12.10.1indirect
npm@pnpm/exe.win32-arm6412.10.1indirect
npm@pnpm/exe.win32-x6412.10.1indirect
npm@testing-library/react^16.3.3indirect
npm@types/react^19.2.18indirect
npm@types/react-dom^19.2.5indirect
npm@vitest/coverage-v8^5.0.0indirect
npmeslint^9.39.5indirect
npmlint-staged^17.4.1indirect
npmpnpm12.10.1indirect
npmprettier^3.9.6indirect
npmreact^19.2.8indirect
npmreact-dom^19.2.8indirect
npmstorybook^10.5.10indirect
npmturbo^2.10.12indirect
npmtypedoc^0.28.20indirect
npmtypescript^6.0.3indirect
npmvitest^5.0.0indirect
Dependency advisories 0

Installing npm:@apitree.cz/cli@1.0.3 pulls in 33 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 — npm.