Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-22 01:01 UTC

guardian / bridget

The bridge between webviews and iOS/Android native code

Thrift · ShellNo license detected★ 7 stars⑂ 1 forksince Dec 2019View on GitHub ↗

guardian/bridget holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Vitality (84/100) and lowest on AI Readiness (20/100). It was last updated 12 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

The GuardianOrganization
578 followers2,072 public repossince Dec 2009

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@guardian/bridget8.14.019,19114596 days ago

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 12 days ago
16.6/36Commit cadence — 24/52 weeks with commits
18/18Commit volume — 112 commits in the last year
10/10OpenSSF Scorecard: Maintained — 17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year112
human_commit_share0.71
days_since_last_push12
active_weeks_last_year24

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 24 days ago
27/27Release cadence — a release every ~16.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv8.14.1-2026-10-28-2
releases_from_tagsno
days_since_latest_release24
mean_days_between_releases16.5
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?

43Weak · 17% of overall
How it's scored
12.6/60Stars — 7 stars
0/25Forks — 1 forks
8.8/15Watchers — 39 watchers
Inputs used
forks1
stars7
watchers39
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateyes
How it's scored
57.1/80Monthly downloads — 19,191 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@guardian/bridget
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads19,191
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?

78Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.8/22.5Commit distribution — top contributor authored 48% of commits
13.5/13.5Contributor breadth — 28 contributors
10/10OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled28
top_contributor_share0.476
How it's scored
34.4/42Issue resolution — 82% of issues closed
25.9/30PR acceptance — 223/258 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs223
open_issues4
closed_issues18
prs_merged_7d0
prs_decided_7d0
prs_merged_30d5
prs_decided_30d5
issue_closed_ratio0.818
closed_unmerged_prs35
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
19.9/25Owner reach — 578 followers of guardian
25/25Track record — 2,072 public repos, account ~16 yr old
Inputs used
followers578
owner_typeOrganization
is_verifiedno
owner_loginguardian
public_repos2,072
account_age_days6,192

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 96 days ago
20/20Version history — 145 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@guardian/bridget
ecosystemsnpm
any_deprecatedno
min_days_since_publish96

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 21 out of 21 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
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 — 1 topics
10/10Wiki
Inputs used
topicsproduction
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?

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 21 out of 21 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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 12 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
0/2.5License — license file not detected
7.5/7.5Maintained — 17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
5/5SAST — SAST tool is run on all commits
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.7
Excluded from scoring (no data or not applicable): 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
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages120
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 120 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

20At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
30/40Legible commit history — 40 of 71 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.563
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 14 of the last 100 commits are automated dependency updates
2/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.14
How it's scored
0/45Type-checkable code — Thrift without a type-check config
0/55Manageable file sizes — no source files detected
Inputs used
primary_languageThrift
largest_source_bytes—
source_files_sampled0
oversized_source_files0
Excluded from scoring (no data or not applicable): Manageable file sizes. Remaining weights renormalized.

Key facts

7GitHub stars
28contributors
112commits, last 12 months
12days since last push
100releases
2bus factor
4open issues
npmpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 6.7 / 10
6.7aggregate

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-11-22 01:00 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests21 out of 21 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 12 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 120

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

RegistryPackageVersionRelation
npm@babel/runtime7.29.2indirect
npm@changesets/apply-release-plan7.1.1indirect
npm@changesets/assemble-release-plan6.0.10indirect
npm@changesets/changelog-git0.2.1indirect
npm@changesets/cli2.31.1indirect
npm@changesets/config3.1.4indirect
npm@changesets/errors0.2.0indirect
npm@changesets/get-dependents-graph2.1.4indirect
npm@changesets/get-release-plan4.0.16indirect
npm@changesets/get-version-range-type0.4.0indirect
npm@changesets/git3.0.4indirect
npm@changesets/logger0.1.1indirect
npm@changesets/parse0.4.3indirect
npm@changesets/pre2.0.2indirect
npm@changesets/read0.6.7indirect
npm@changesets/should-skip-package0.1.2indirect
npm@changesets/types4.1.0indirect
npm@changesets/types6.1.0indirect
npm@changesets/write0.4.0indirect
npm@creditkarma/thrift-parser1.2.0indirect
npm@creditkarma/thrift-server-core1.0.4indirect
npm@creditkarma/thrift-typescript3.7.6indirect
npm@inquirer/external-editor1.0.3indirect
npm@manypkg/find-root1.1.0indirect
npm@manypkg/get-packages1.1.3indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@types/fs-extra7.0.0indirect
npm@types/lodash4.14.149indirect
npm@types/node12.20.55indirect
npm@types/node25.3.3indirect
npmansi-colors4.1.3indirect
npmansi-regex5.0.1indirect
npmargparse1.0.10indirect
npmargparse2.0.1indirect
npmarray-union2.1.0indirect
npmbalanced-match1.0.0indirect
npmbetter-path-resolve1.0.0indirect
npmbrace-expansion1.1.21indirect
npmbraces3.0.3indirect
npmchardet2.1.1indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.6indirect
npmdetect-indent6.1.0indirect
npmdir-glob3.0.1indirect
npmenquirer2.4.1indirect
npmesprima4.0.1indirect
npmextendable-error0.1.7indirect
npmfast-glob3.3.3indirect
npmfastq1.20.1indirect
npmfill-range7.1.1indirect
npmfind-up4.1.0indirect
npmfs-extra7.0.1indirect
npmfs-extra8.1.0indirect
npmfs.realpath1.0.0indirect
npmglob7.1.6indirect
npmglob-parent5.1.2indirect
npmglobby11.1.0indirect
npmgraceful-fs4.2.3indirect
npmhuman-id4.1.1indirect
npmiconv-lite0.7.2indirect
npmignore5.3.2indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-subdir1.2.0indirect
npmis-windows1.0.2indirect
npmisexe2.0.0indirect
npmjs-yaml3.15.2indirect
npmjs-yaml4.3.2indirect
npmjsonfile4.0.0indirect
npmlocate-path5.0.0indirect
npmlodash4.18.1indirect
npmlodash.startcase4.4.0indirect
npmmerge21.4.1indirect
npmmicromatch4.0.8indirect
npmminimatch3.1.5indirect
npmmri1.2.0indirect
npmonce1.4.0indirect
npmoutdent0.5.0indirect
npmp-filter2.1.0indirect
npmp-limit2.3.0indirect
npmp-locate4.1.0indirect
npmp-map2.1.0indirect
npmp-try2.2.0indirect
npmpackage-manager-detector0.2.0indirect
npmpath-exists4.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-key3.1.1indirect
npmpath-type4.0.0indirect
npmpicocolors1.1.1indirect
npmpicomatch2.3.2indirect
npmpify4.0.1indirect
npmprettier2.8.8indirect
npmqueue-microtask1.2.3indirect
npmread-yaml-file1.1.0indirect
npmresolve-from5.0.0indirect
npmreusify1.1.0indirect
npmrun-parallel1.2.0indirect
npmsafer-buffer2.1.2indirect
npmsemver7.7.4indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmslash3.0.0indirect
npmspawndamnit3.0.1indirect
npmsprintf-js1.0.3indirect
npmstrip-ansi6.0.1indirect
npmstrip-bom3.0.0indirect
npmterm-size2.2.1indirect
npmto-regex-range5.0.1indirect
npmtypescript3.5.3indirect
npmtypescript5.3.3indirect
npmundici-types7.18.2indirect
npmuniversalify0.1.2indirect
npmwhich2.0.2indirect
npmwrappy1.0.2indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 120 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

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.