Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 02:15 UTC

nibble-4bits / codewars-solutions-scraper

A scraper that gets the solutions of all of the CodeWars katas you have solved

JavaScriptGPL-3.0★ 3 stars⑂ 2 forkssince May 2020View on GitHub ↗
KindCommand-line toolLibraryhow this is determined
#codewars#solutions#scraper#katas

nibble-4bits/codewars-solutions-scraper holds a health index of 15 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (45/100) and lowest on AI Readiness (21/100). It was last updated 1077 days ago. A single contributor accounts for most of its recent work.

15
overall / 100
Critical

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.

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

Ownership

Luis De AndaPersonal account
43 followers37 public repossince Apr 2018@Wizeline

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
npmcodewars-solutions-scraper1.0.81991894 days agocodewarsscrapersolutionsproblemskataspuppeteer

Metrics by category

Vitality

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

25At Risk · 21% of overall

Development activity

1Critical
How it's scored
0/36Push recency — last push 1,077 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share0.957
days_since_last_push1,077
active_weeks_last_year0

Release discipline

60Moderate
How it's scored
27/27Ships releases — 9 releases published
0/36Release recency — latest release 1,894 days ago
27/27Release cadence — a release every ~43.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count9
latest_release_tagv1.0.8
releases_from_tagsno
days_since_latest_release1,894
mean_days_between_releases43.7
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

Popularity & adoption

5Critical
How it's scored
4.9/60Stars — 3 stars
0/25Forks — 2 forks
0/15Watchers — 1 watchers
Inputs used
forks2
stars3
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
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

Ecosystem adoption (downloads)

22At Risk
How it's scored
17.3/80Monthly downloads — 19 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescodewars-solutions-scraper
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads19
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?

45Weak · 23% of overall

Maintainer resilience (bus factor)

13Critical
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1

Issue & PR responsiveness

51Moderate
How it's scored
14/42Issue resolution — 33% of issues closed
30/30PR acceptance — 5/5 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/25 approved changesets -- score normalized to 0
Inputs used
merged_prs5
open_issues2
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.333
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): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

57Moderate
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
11.8/25Owner reach — 43 followers of nibble-4bits
23.5/25Track record — 37 public repos, account ~8 yr old
Inputs used
followers43
owner_typeUser
is_verified—
owner_loginnibble-4bits
public_repos37
account_age_days3,085
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

69Good
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 1,894 days ago
20/20Version history — 9 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescodewars-solutions-scraper
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,894

Engineering Quality

Are baseline engineering and documentation practices in place?

25At Risk · 19% of overall

Engineering practices

1Critical
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-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicscodewars, solutions, scraper, katas
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?

36Weak · 16% of overall

Security posture

26At Risk
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 — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/25 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
0/7.5Vulnerabilities — 23 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

76Good
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
7.4/25Indirect dependencies free of known advisories — 2 affected: extract-zip 2.0.1 (high 8.1), tmp 0.0.33 (high 7.5)
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 403 days ago
Inputs used
sourceosv
advisories4
affected_packages2
assessed_packages83
unassessed_packages0
affected_by_severityhigh 2
direct_affected_packages0
Matched the npm:codewars-solutions-scraper@1.0.8 runtime dependency closure — what installing the published package pulls in — 83 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.

21At Risk · 4% of overall

Agent context & guidance

6Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
5.6/40Legible commit history — 7 of 67 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.104
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

20At Risk
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 70
8/8Automated maintenance — 3 of the last 70 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.043
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

55Moderate
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/2 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes6,835
source_files_sampled2
oversized_source_files0

Key facts

3GitHub stars
1contributors
0commits, last 12 months
1,077days since last push
9releases
1bus factor
2open issues
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 ★ / 2 ⇿
0Stars
2Forks

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.

111222212022-052022-052022-05
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-09-14 02:15 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/25 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities23 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
npmchalk^4.0.0package.json
npmcommander^5.1.0package.json
npminquirer^7.1.0package.json
npmloglevel^1.6.8package.json
npmloglevel-plugin-prefix^0.8.4package.json
npmpuppeteer^3.1.0package.json
All dependencies 84

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

RegistryPackageVersionRelation
npmchalk3.0.0direct
npmchalk4.0.0direct
npmcommander5.1.0direct
npminquirer7.1.0direct
npmloglevel1.6.8direct
npmloglevel-plugin-prefix0.8.4direct
npmpuppeteer3.1.0direct
npm@types/color-name1.1.1indirect
npm@types/node14.0.5indirect
npm@types/yauzl2.9.1indirect
npmagent-base5.1.1indirect
npmansi-escapes4.3.1indirect
npmansi-regex5.0.0indirect
npmansi-styles4.2.1indirect
npmbalanced-match1.0.0indirect
npmbase64-js1.3.1indirect
npmbl4.0.3indirect
npmbrace-expansion1.1.11indirect
npmbuffer5.6.0indirect
npmbuffer-crc320.2.13indirect
npmchardet0.7.0indirect
npmchownr1.1.4indirect
npmcli-cursor3.1.0indirect
npmcli-width2.2.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmdebug4.1.1indirect
npmemoji-regex8.0.0indirect
npmend-of-stream1.4.4indirect
npmescape-string-regexp1.0.5indirect
npmexternal-editor3.1.0indirect
npmextract-zip2.0.0indirect
npmfd-slicer1.1.0indirect
npmfigures3.2.0indirect
npmfs-constants1.0.0indirect
npmfs.realpath1.0.0indirect
npmget-stream5.1.0indirect
npmglob7.1.6indirect
npmhas-flag4.0.0indirect
npmhttps-proxy-agent4.0.0indirect
npmiconv-lite0.4.24indirect
npmieee7541.1.13indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-fullwidth-code-point3.0.0indirect
npmlodash4.17.21indirect
npmmime2.4.5indirect
npmmimic-fn2.1.0indirect
npmminimatch3.0.4indirect
npmmkdirp-classic0.5.3indirect
npmms2.1.2indirect
npmmute-stream0.0.8indirect
npmonce1.4.0indirect
npmonetime5.1.0indirect
npmos-tmpdir1.0.2indirect
npmpath-is-absolute1.0.1indirect
npmpend1.2.0indirect
npmprogress2.0.3indirect
npmproxy-from-env1.1.0indirect
npmpump3.0.0indirect
npmreadable-stream3.6.0indirect
npmrestore-cursor3.1.0indirect
npmrimraf3.0.2indirect
npmrun-async2.4.1indirect
npmrxjs6.5.5indirect
npmsafe-buffer5.2.1indirect
npmsafer-buffer2.1.2indirect
npmsignal-exit3.0.3indirect
npmstring-width4.2.0indirect
npmstring_decoder1.3.0indirect
npmstrip-ansi6.0.0indirect
npmsupports-color7.1.0indirect
npmtar-fs2.1.0indirect
npmtar-stream2.1.2indirect
npmthrough2.3.8indirect
npmtmp0.0.33indirect
npmtslib1.13.0indirect
npmtype-fest0.11.0indirect
npmunbzip2-stream1.4.2indirect
npmutil-deprecate1.0.2indirect
npmwrappy1.0.2indirect
npmws7.3.0indirect
npmyauzl2.10.0indirect
Dependency advisories 2

Installing npm:codewars-solutions-scraper@1.0.8 pulls in 83 packages, direct and transitive: 2 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
extract-zip2.0.1indirecthigh2—
tmp0.0.33indirecthigh20.2.6

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with nibble-4bits/codewars-solutions-scraper. Read them side by side →

98apify/crawleeCrawlee—A web scraping and browser automation library for Node.js to build reliable crawlers. In JavaScript and TypeScript. Extract data for AI, LLMs, RAG, or GPTs. Download HTML, PDF, JPG, PNG, and other files from websites. Works with Puppeteer, Playwright, Cheerio, JSDOM, and raw HTTP. Both headful and headless mode. With proxy rotation.Exceptional92apify/apify-sdk-jsApify SDK monorepoExcellent90apify/fingerprint-suiteBrowser fingerprinting tools for anonymizing your scrapers. Developed by Apify.Excellent59cherchyk/MCPBrowserModerate81html2rss/html2rss📰 Build RSS 2.0 feeds from websites (and JSON APIs) automatically or with a few CSS selectors.Excellent59fanyong920/jvppeteerJava API For Chrome and FirefoxModerate

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.