Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-10 15:50 UTC

janekolszak / poland

Administrative division of Poland

TypeScriptMIT★ 0 stars⑂ 0 forkssince Oct 2022View on GitHub ↗

janekolszak/poland holds a health index of 29 out of 100, placing it in the At Risk band. It scores highest on Vitality (50/100) and lowest on Engineering Quality (21/100). It was last updated 18 days ago. A single contributor accounts for most of its recent work.

29
overall / 100
At Risk

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.

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

Ownership

Jan OlszakPersonal account
22 followers46 public repossince Dec 2012

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
npm@janekolszak/poland1.2.03051218 days agovivodeshipcommunitycountygminapowiatmiasto

Metrics by category

Vitality

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

50Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 18 days ago
0.7/36Commit cadence1/52 weeks with commits
4.3/18Commit volume2 commits in the last year
1/10OpenSSF Scorecard: Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year2
human_commit_share1
days_since_last_push18
active_weeks_last_year1
How it's scored
16.2/27Ships releases10 version tags (no GitHub releases)
36/36Release recencylatest release 18 days ago
12.6/27Release cadencea release every ~139 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count10
latest_release_tagv1.2.0
releases_from_tagsyes
days_since_latest_release18
mean_days_between_releases139
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?

28At Risk · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars0
watchers1
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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
33.1/80Monthly downloads305 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@janekolszak/poland
dependents
ecosystemsnpm
total_downloads
monthly_downloads305
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?

37Weak · 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
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
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_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
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): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
9.8/25Owner reach22 followers of janekolszak
24.2/25Track record46 public repos, account ~13 yr old
Inputs used
followers22
owner_typeUser
is_verified
owner_loginjanekolszak
public_repos46
account_age_days4,981
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 18 days ago
20/20Version history12 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@janekolszak/poland
ecosystemsnpm
any_deprecatedno
min_days_since_publish18

Engineering Quality

Are baseline engineering and documentation practices in place?

21At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
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?

41Weak · 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/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0.8/7.5Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate2.6
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/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages2
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:@janekolszak/poland@1.2.0 runtime dependency closure — what installing the published package pulls in — 2 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.

29At Risk · 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 34 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
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 34
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/7 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes11,150
source_files_sampled7
oversized_source_files0

Key facts

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

More detail

OpenSSF Scorecard 2.6 / 10
2.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-08-10 15:50 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
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npm@final-hill/multi-key-map^1.1.4package.json
npmmany-keys-map^2.0.0package.json
All dependencies 53

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

RegistryPackageVersionRelation
npm@final-hill/multi-key-map1.1.4direct
npmmany-keys-map2.0.0direct
npm@cspotcode/source-map-support0.8.1indirect
npm@jridgewell/resolve-uri3.1.0indirect
npm@jridgewell/sourcemap-codec1.4.14indirect
npm@jridgewell/trace-mapping0.3.9indirect
npm@tsconfig/node101.0.9indirect
npm@tsconfig/node121.0.11indirect
npm@tsconfig/node141.0.3indirect
npm@tsconfig/node161.0.3indirect
npm@types/node18.11.3indirect
npmacorn8.8.0indirect
npmacorn-walk8.2.0indirect
npmansi-styles3.2.1indirect
npmansi-styles4.3.0indirect
npmarg4.1.3indirect
npmarray-back3.1.0indirect
npmarray-back4.0.2indirect
npmchalk2.4.2indirect
npmchalk4.1.2indirect
npmcolor-convert1.9.3indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.3indirect
npmcolor-name1.1.4indirect
npmcommand-line-args5.2.1indirect
npmcommand-line-usage6.1.3indirect
npmcreate-require1.1.1indirect
npmcsv6.2.1indirect
npmcsv-generate4.2.0indirect
npmcsv-parse5.3.1indirect
npmcsv-stringify6.2.0indirect
npmdeep-extend0.6.0indirect
npmdiff4.0.2indirect
npmescape-string-regexp1.0.5indirect
npmfind-replace3.0.0indirect
npmhas-flag3.0.0indirect
npmhas-flag4.0.0indirect
npmlodash.camelcase4.3.0indirect
npmmake-error1.3.6indirect
npmreduce-flatten2.0.0indirect
npmstream-transform3.2.0indirect
npmstring-format2.0.0indirect
npmsupports-color5.5.0indirect
npmsupports-color7.2.0indirect
npmtable-layout1.0.2indirect
npmts-command-line-args2.3.1indirect
npmts-node10.9.1indirect
npmtypescript4.8.4indirect
npmtypical4.0.0indirect
npmtypical5.2.0indirect
npmv8-compile-cache-lib3.0.1indirect
npmwordwrapjs4.0.1indirect
npmyn3.1.1indirect
Dependency advisories 0

Installing npm:@janekolszak/poland@1.2.0 pulls in 2 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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.