Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 06:58 UTC

nyaruka / temba-components

General web components for site building

TypeScriptCustom license★ 5 stars⑂ 7 forkssince Mar 2020archivedView on GitHub ↗

nyaruka/temba-components holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Engineering Quality (84/100) and lowest on Community & Adoption (38/100). The repository is archived, so no further maintenance is expected.

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

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

Ownership

nyarukaOrganization
52 followers87 public repossince Jun 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@nyaruka/temba-components0.174.09,51749236 days ago

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
18/36Push recency — last push 35 days ago
30.5/36Commit cadence — 44/52 weeks with commits
18/18Commit volume — 855 commits in the last year
0/10OpenSSF Scorecard: Maintained — project is archived
Inputs used
commits_last_year855
human_commit_share1
days_since_last_push35
active_weeks_last_year44
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 36 days ago
27/27Release cadence — a release every ~0.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv0.174.0
releases_from_tagsyes
days_since_latest_release36
mean_days_between_releases0.9
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?

38Weak · 17% of overall
How it's scored
9.8/60Stars — 5 stars
6.5/25Forks — 7 forks
0/15Watchers — 2 watchers
Inputs used
forks7
stars5
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
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
53/80Monthly downloads — 9,517 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@nyaruka/temba-components
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads9,517
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.1/22.5Commit distribution — top contributor authored 86% of commits
8.1/13.5Contributor breadth — 6 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.861
How it's scored
36.7/42Issue resolution — 87% of issues closed
28.3/30PR acceptance — 897/952 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/3 approved changesets -- score normalized to 0
Inputs used
merged_prs897
open_issues18
closed_issues125
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.874
closed_unmerged_prs55
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
30/30Ownership backing — organization-owned
0/20Verified domain
12.4/25Owner reach — 52 followers of nyaruka
25/25Track record — 87 public repos, account ~16 yr old
Inputs used
followers52
owner_typeOrganization
is_verifiedno
owner_loginnyaruka
public_repos87
account_age_days5,939

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 36 days ago
20/20Version history — 492 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@nyaruka/temba-components
ecosystemsnpm
any_deprecatedno
min_days_since_publish36

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 2 out of 2 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
How it's scored
30/30README
25/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_diryes
has_descriptionyes

Security

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

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 2 out of 2 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 — Found 0/3 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
0/7.5Maintained — project is archived
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
0/7.5Vulnerabilities — 75 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: image-size 1.2.1 (high 7.5)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 92 days ago
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages46
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages1
Matched the npm:@nyaruka/temba-components@0.174.0 runtime dependency closure — what installing the published package pulls in — 46 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
19.7/40Legible commit history — 37 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.37
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.js
11/11Static type checking — tsconfig.json
10/10Reproducible environment — devcontainer, Dockerfile
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
lockfiles—
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontaineryes
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
53.5/55Manageable file sizes — 11/400 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes157,801
source_files_sampled400
oversized_source_files11

Key facts

5GitHub stars
6contributors
855commits, last 12 months
35days since last push
100releases
1bus factor
18open 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 ★ / 7 ⇿
0Stars
7Forks

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.

123456612021-012022-112024-09

Each point covers 4 days.

OpenSSF Scorecard 3.8 / 10
3.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-09-11 06:57 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/3 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintainedproject is archived
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
0Vulnerabilities75 existing vulnerabilities detected
Direct dependencies 22
RegistryPackageVersion constraintManifest
npm@jsplumb/browser-ui^6.2.10package.json
npm@lit/localize^0.12.2package.json
npm@open-wc/lit-helpers^0.7.0package.json
npmcentrifuge^5.7.0package.json
npmchart.js^4.5.1package.json
npmchartjs-adapter-luxon^1.3.1package.json
npmchartjs-plugin-datalabels^2.2.0package.json
npmcolor-hash^2.0.2package.json
npmcroppie^2.6.5package.json
npmgeojson^0.5.0package.json
npmimage-size^1.1.1package.json
npmimmer10package.json
npmleaflet1.5.1package.json
npmlit3.3.2package.json
npmlit-element^4.2.2package.json
npmlit-html^3.3.2package.json
npmluxon3.7package.json
npmremarkable^2.0.1package.json
npmserialize-javascript^7.0.3package.json
npmtiny-lru^11.2.5package.json
npmuuid^14.0.0package.json
npmzustand^5.0.3package.json
All dependencies 73

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

RegistryPackageVersionRelation
npm@jsplumb/browser-ui^6.2.10direct
npm@lit/localize^0.12.2direct
npm@open-wc/lit-helpers^0.7.0direct
npmcentrifuge^5.7.0direct
npmchart.js^4.5.1direct
npmchartjs-adapter-luxon^1.3.1direct
npmchartjs-plugin-datalabels^2.2.0direct
npmcolor-hash^2.0.2direct
npmcroppie^2.6.5direct
npmgeojson^0.5.0direct
npmimage-size^1.1.1direct
npmimmer10direct
npmleaflet1.5.1direct
npmlit3.3.2direct
npmlit-element^4.2.2direct
npmlit-html^3.3.2direct
npmluxon3.7direct
npmremarkable^2.0.1direct
npmserialize-javascript^7.0.3direct
npmtiny-lru^11.2.5direct
npmuuid^14.0.0direct
npmzustand^5.0.3direct
npm@lit/localize-tools^0.8.1indirect
npm@open-wc/testing4.0.0indirect
npm@rollup/plugin-commonjs^29.0.0indirect
npm@rollup/plugin-image^3.0.3indirect
npm@rollup/plugin-node-resolve^16.0.3indirect
npm@rollup/plugin-replace^6.0.2indirect
npm@rollup/plugin-terser^0.4.4indirect
npm@rollup/plugin-typescript^12.3.0indirect
npm@types/leaflet1.4.4indirect
npm@types/mocha^10.0.0indirect
npm@types/node22.13.0indirect
npm@types/remarkable^2.0.1indirect
npm@typescript-eslint/eslint-plugin^7.5.0indirect
npm@typescript-eslint/parser^7.5.0indirect
npm@web/dev-server^0.4.6indirect
npm@web/dev-server-esbuild^1.0.5indirect
npm@web/dev-server-rollup^0.6.4indirect
npm@web/test-runner0.20.2indirect
npm@web/test-runner-puppeteer0.15.0indirect
npmauto-changelog*indirect
npmbusboy^1.6.0indirect
npmconcurrently^9.2.1indirect
npmdeepmerge^4.3.1indirect
npmdynamicpixelmatch^0.0.2indirect
npmeslint^8.29.0indirect
npmeslint-plugin-html^7.1.0indirect
npmeslint-plugin-import^2.26.0indirect
npmeslint-plugin-lit^1.10.1indirect
npmeslint-plugin-lit-a11y^4.1.1indirect
npmeslint-plugin-no-only-tests^3.1.0indirect
npmeslint-plugin-wc^1.2.0indirect
npmfprint^2.0.1indirect
npmhtmlclean^3.0.8indirect
npmlint-staged^10.0.0indirect
npmminio^8.0.5indirect
npmnode-fetch^3.3.2indirect
npmoslllo-svg-fixer^2.2.0indirect
npmpixelmatch^5.2.1indirect
npmpngjs^6.0.0indirect
npmprettier^3.8.1indirect
npmrimraf^2.6.3indirect
npmrollup^4.0.0indirect
npmrollup-plugin-copy^3.4.0indirect
npmrollup-plugin-svg-import^3.0.0indirect
npmrollup-plugin-url^3.0.1indirect
npmshelljs^0.8.5indirect
npmsinon^21.0.0indirect
npmsvgstore^3.0.1indirect
npmtslib2.8.1indirect
npmtypescript5.9.3indirect
npmyargs^17.7.2indirect
Dependency advisories 1

Installing npm:@nyaruka/temba-components@0.174.0 pulls in 46 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
image-size1.2.1directhigh2—

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.