Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 11:16 UTC

clakeboy / react-bootstrap-v4

TypeScript · JavaScriptMIT★ 5 stars⑂ 1 forksince Mar 2018View on GitHub ↗

clakeboy/react-bootstrap-v4 holds a health index of 30 out of 100, placing it in the At Risk band. It scores highest on AI Readiness (43/100) and lowest on Vitality (29/100). It was last updated 40 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Clake leePersonal account
5 followers35 public repossince May 2014

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@clake/react-bootstrap42.6.172,49236440 days agoreactbootstrapv4

Metrics by category

Vitality

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

29At Risk · 21% of overall
How it's scored
18/36Push recency — last push 40 days ago
13.2/36Commit cadence — 19/52 weeks with commits
13.9/18Commit volume — 34 commits in the last year
2/10OpenSSF Scorecard: Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year34
human_commit_share1
days_since_last_push40
active_weeks_last_year19
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?

36Weak · 17% of overall
How it's scored
9.8/60Stars — 5 stars
0/25Forks — 1 forks
0/15Watchers — 2 watchers
Inputs used
forks1
stars5
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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
45.3/80Monthly downloads — 2,492 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@clake/react-bootstrap4
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,492
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 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
0/10OpenSSF Scorecard: Contributors — project 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 resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
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_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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
5.6/25Owner reach — 5 followers of clakeboy
23.3/25Track record — 35 public repos, account ~12 yr old
Inputs used
followers5
owner_typeUser
is_verified—
owner_loginclakeboy
public_repos35
account_age_days4,533
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 40 days ago
20/20Version history — 364 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@clake/react-bootstrap4
ecosystemsnpm
any_deprecatedno
min_days_since_publish40

Engineering Quality

Are baseline engineering and documentation practices in place?

38Weak · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
16/16Linter config — .eslintrc
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

42Weak · 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
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
1.5/7.5Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate2.8
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 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_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:@clake/react-bootstrap4@2.6.17 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.

43Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
12.8/40Legible commit history — 24 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.24
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — .eslintrc
11/11Static type checking — tsconfig.json
0/10Reproducible environment
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 — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
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 code — TypeScript (statically typed)
54.3/55Manageable file sizes — 1/84 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes700,147
source_files_sampled84
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

5GitHub stars
1contributors
34commits, last 12 months
40days since last push
0releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 2.8 / 10
2.8aggregate

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-19 11:16 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
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmbootstrap^5.3.2package.json
npmclassnames^2.3.1package.json
All dependencies 75

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

RegistryPackageVersionRelation
npmbootstrap^5.3.2direct
npmclassnames^2.3.1direct
npm@babel/core^7.3.4indirect
npm@babel/plugin-proposal-class-properties^7.3.4indirect
npm@babel/plugin-proposal-export-default-from^7.2.0indirect
npm@babel/plugin-proposal-nullish-coalescing-operator^7.8.3indirect
npm@babel/plugin-proposal-optional-chaining^7.9.0indirect
npm@babel/plugin-syntax-dynamic-import^7.2.0indirect
npm@babel/plugin-transform-runtime^7.3.4indirect
npm@babel/preset-env^7.3.4indirect
npm@babel/preset-react^7.0.0indirect
npm@babel/preset-typescript^7.17.12indirect
npm@babel/register^7.0.0indirect
npm@babel/runtime^7.3.4indirect
npm@types/bootstrap^5.2.7indirect
npm@types/browser-sync^2.29.0indirect
npm@types/classnames^2.3.1indirect
npm@types/connect-history-api-fallback^1.5.4indirect
npm@types/gulp^4.0.17indirect
npm@types/gulp-babel^6.1.33indirect
npm@types/gulp-header^2.0.4indirect
npm@types/gulp-plumber^0.0.37indirect
npm@types/gulp-sourcemaps^0.0.38indirect
npm@types/gulp-util^3.0.41indirect
npm@types/jquery^3.5.18indirect
npm@types/prop-types^15.7.5indirect
npm@types/react^18.0.9indirect
npm@types/react-dom^18.2.6indirect
npm@types/through2^2.0.41indirect
npm@types/webpack^5.28.5indirect
npm@types/webpack-hot-middleware^2.25.9indirect
npm@typescript-eslint/eslint-plugin^5.25.0indirect
npm@typescript-eslint/parser^5.25.0indirect
npmbabel-loader^8.0.5indirect
npmbrowser-sync^2.24.5indirect
npmconnect-history-api-fallback^1.5.0indirect
npmcss-loader^0.28.7indirect
npmdel^3.0.0indirect
npmeslint^7.1.0indirect
npmeslint-loader^4.0.2indirect
npmeslint-plugin-react^7.30.0indirect
npmeslint-plugin-react-hooks^4.5.0indirect
npmexpress^4.17.1indirect
npmfile-loader^1.1.5indirect
npmgulp^4.0.2indirect
npmgulp-babel^8.0.0indirect
npmgulp-concat^2.6.1indirect
npmgulp-header^1.8.9indirect
npmgulp-load-plugins^1.5.0indirect
npmgulp-plumber^1.2.1indirect
npmgulp-sourcemaps^2.6.5indirect
npmgulp-util^3.0.8indirect
npmless^4.2.0indirect
npmless-loader^7.0.0indirect
npmmini-css-extract-plugin^0.4.0indirect
npmmultiparty^4.2.2indirect
npmpath^0.12.7indirect
npmprocess^0.11.10indirect
npmprop-types^15.8.1indirect
npmraw-loader^4.0.0indirect
npmreact^18.2.0indirect
npmreact-dom^18.2.0indirect
npmreact-markdown^8.0.7indirect
npmreact-router^4.2.0indirect
npmreact-router-dom^4.2.2indirect
npmreact-syntax-highlighter^12.2.1indirect
npmreact-to-typescript-definitions^3.1.0indirect
npmstyle-loader^0.23.1indirect
npmthrough2^4.0.2indirect
npmtypescript^4.6.4indirect
npmwebpack^4.47.0indirect
npmwebpack-dev-middleware^3.1.0indirect
npmwebpack-hot-middleware^2.21.0indirect
npmwebpack-merge^4.1.1indirect
npmwhatwg-fetch^3.0.0indirect
Dependency advisories 0

Installing npm:@clake/react-bootstrap4@2.6.17 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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.