NavigaraNavigara
OrganizationsDistributionCompareResearch
NavigaraNavigara
OrganizationsDistributionCompareResearch
All developers

Guy Bedford

Developer

Guy Bedford

gbedford@cloudflare.com

95 commits~9 files/commit

Performance

2026Previous year

Insights

Key patterns and highlights from this developer's activity.

Peak MonthSep'25545 performance
Growth Trend↓87%vs prior period
Avg Files/Commit9files per commit
Active Days51of 455 days
Top Repoworkers-rs70 commits

Effort Over Time

Breakdown of growth, maintenance, and fixes effort over time.

Bug Behavior

Beta

Bugs introduced vs. fixed over time.

Investment Quality

Beta

Reclassifies engineering effort based on bug attribution. Commits that introduced bugs are retrospectively counted as poor investments.

33%Productive TimeGrowth 71% + Fixes 29%
25%Maintenance Time
42%Wasted Time
How it works

Methodology

Investment Quality reclassifies engineering effort based on bug attribution data. Commits identified as buggy origins (those that introduced bugs later fixed by someone) have their grow and maintenance time moved into the Wasted Time category. Their waste (fix commits) remains counted as productive. All other commits retain their standard classification: grow is productive, maintenance is maintenance, and waste (fixes) is productive.

Relationship to Growth / Maintenance / Fixes

The standard model classifies commits as Growth, Maintenance, or Fixes. Investment Quality adds a quality lens: a commit that introduced a bug is retrospectively counted as a poor investment — the engineering time spent on it was wasted because it ultimately required additional fix work. Fix commits (Fixes in the standard model) are reframed as productive, because fixing bugs is valuable work.

Proposed API Endpoint

Currently computed client-side from commit and bug attribution data. Ideal server-side endpoint:

POST /v1/organizations/{orgId}/investment-quality
Content-Type: application/json

Request:
{
  "startTime": "2025-01-01T00:00:00Z",
  "endTime": "2025-12-31T23:59:59Z",
  "bucketSize": "BUCKET_SIZE_MONTH",
  "groupBy": ["repository_id" | "deliverer_email"]
}

Response:
{
  "productivePct": 74,
  "maintenancePct": 18,
  "wastedPct": 8,
  "buckets": [
    {
      "bucketStart": "2025-01-01T00:00:00Z",
      "productive": 4.2,
      "maintenance": 1.8,
      "wasted": 0.6
    }
  ]
}

Recent Activity

Latest analyzed commits from this developer.

HashMessageDateFilesEffort
f6cdab2This commit introduces **support for source phase imports** within **Wrangler**, enabling developers to use the `import source` syntax for advanced module loading. It configures `esbuild` to recognize this syntax, ensuring that **WASM modules imported via `import source` are correctly processed**, copied to the output, and included in the worker bundle, even when `--no-bundle` is specified. This **new capability** also improves **Wrangler's worker format detection**, accurately identifying the 'modules' format when source phase imports are present. Overall, this **enhances Wrangler's bundling and deployment logic**, providing more robust handling for modern JavaScript module patterns.Mar 255grow
5602399This commit introduces a **robust build locking mechanism** within the **`worker-build` subsystem** to prevent concurrent build processes from corrupting shared output files. It implements a new `BuildLock` that directs all build output into a temporary staging directory (`build/.tmp/`) and uses an mtime-based heartbeat to coordinate and wait for other active builds. This **bug fix** addresses a critical concurrency issue by ensuring that `wrangler`'s worker builds are atomic. The change significantly enhances the **reliability and stability** of worker deployments by preventing build failures and inconsistent states when multiple commands trigger builds simultaneously.Feb 2510waste
4c30cd5This commit **introduces a comprehensive performance benchmarking suite** for the `workers-rs` project, establishing a **new capability** for continuous performance monitoring. It adds a dedicated `benchmark/` module containing Rust worker code (`benchmark/src/lib.rs`) for testing streaming and parallel sub-requests, along with Node.js scripts (`benchmark/run.js`, `benchmark/codspeed-convert.js`) to execute benchmarks against a worker server using Miniflare and convert results for CodSpeed. A new **GitHub Actions workflow** (`.github/workflows/codspeed.yml`) is also integrated to automate benchmark runs on push and pull requests, providing crucial insights into performance regressions and improvements for `workers-rs` applications. This suite allows developers to easily run and analyze performance metrics locally and within CI.Feb 2511grow
73d1b8cThis commit performs a **dependency update** for the `wasm-bindgen` toolchain, upgrading it to version `0.2.113`. This **maintenance** task involves updating the `Cargo.toml` file to reflect the new dependency version and synchronizing the `wasm-bindgen` Git submodule reference. The change ensures the project benefits from the latest features, bug fixes, and performance improvements within the **WebAssembly build process** and its Rust-to-JavaScript bindings.Feb 243–
0e08d09This commit performs a **dependency update** for the **WebAssembly (Wasm) binding generation** toolchain, advancing `wasm-bindgen` and its related crates to version `0.2.112`. This **maintenance** task updates the `Cargo.toml` dependencies and the `wasm-bindgen` git submodule, ensuring the project utilizes the latest features and bug fixes from the `wasm-bindgen` ecosystem. Additionally, the `LATEST_WASM_BINDGEN_VERSION` constant in `worker-build/src/versions.rs` is updated to reflect this new baseline. This upgrade improves the overall stability and capabilities of **Rust-to-Wasm compilation and JavaScript interoperability**.Feb 243maint
08f9876This commit delivers a **bug fix** and **refactoring** for the **`SecretStore`** module, resolving issues where `SecretStore::get()` could incorrectly return `None` or silently fail. It **removes an unnecessary `Fetcher` indirection** when constructing `SecretStore` from its JavaScript binding, ensuring the direct use of the binding's `.get()` method for proper method dispatch. Additionally, the commit **stops silently swallowing JavaScript errors** within `SecretStore::get()`, instead propagating them via `Result` to improve error visibility and reliability, aligning its behavior with the `Storage::get` pattern. This change significantly enhances the **runtime stability** and **predictability** of secret retrieval operations.Feb 242waste
29530cdThis commit primarily **updates the `wasm-bindgen` dependency** to version 0.2.110, alongside `web-sys` and the Rust toolchain, as a **maintenance** task. It also includes significant **refactoring** across various modules. Specifically, it standardizes string formatting for error messages and debug output in `test`, `worker-build`, and `worker-macros` components. Furthermore, it enhances the robustness of the **`worker` runtime** by updating `Closure` usage to unwind-safe variants like `Closure::wrap_assert_unwind_safe` in `Delay`, `DurableObject`, and `WebSocket` implementations.Feb 2120maint
5f06bb0This commit introduces **support for the `--panic-unwind` build option** for `worker-build`, enabling Rust panics within **Cloudflare Workers** to unwind rather than immediately aborting. This **new capability** involves updating the `worker-macros` and `worker` crates to wrap critical futures with `AssertUnwindSafe`, ensuring proper panic propagation and recovery in modules like `durable_object`, `event` handlers, and `wait_until` calls. The build process now conditionally inserts `criticalError` logic into the JavaScript shim, and comprehensive **testing infrastructure** has been added to validate unwind behavior. This significantly enhances the robustness and error handling capabilities of Rust-based Workers by allowing for more graceful panic recovery.Jan 2317grow
70fed58This commit **updates the Rust toolchain** configuration for the project, specifically upgrading the channel from version `1.83.0` to `1.87.0` within the `rust-toolchain.toml` file. It also introduces a default profile for the toolchain, standardizing its usage. This is a **maintenance update** to the **Continuous Integration (CI)** infrastructure, addressing potential compatibility issues or preparing for new features. The change ensures the project builds and tests against a more recent and potentially more stable Rust version, thereby improving **build reliability** and **developer consistency**.Jan 201maint
fd7bf46This commit **updates the project documentation** by removing an outdated reference to `utils::set_panic_hook()` from the example code within `README.md`. It also **deletes the associated 'Caveats' section**, which is no longer relevant to the current project state. This **documentation fix** ensures that users are presented with accurate and current information, preventing confusion when setting up panic handling. The change primarily impacts the **readability and correctness of the `README.md`**, improving the initial user experience by removing deprecated instructions.Jan 201maint
c92654dThis commit introduces a **new feature** to the **`worker-build`** system, enabling support for older `wasm-bindgen` versions. It **refactors** the `WasmBindgen` struct in `worker-build/src/binary.rs` to dynamically accept a version string, allowing projects to specify and use older `wasm-bindgen` versions. To facilitate this, the `Cargo.toml` was updated to downgrade `wasm-bindgen` dependencies, and version constants in `worker-build/src/versions.rs` were adjusted. Additionally, the `check_dependency_version` function in `worker-build/src/lockfile.rs` was updated to return the actual version found, improving the robustness of dependency checks. This change significantly improves compatibility and flexibility for projects that rely on specific or older `wasm-bindgen` toolchains.Jan 155maint
2b5844fThis commit performs a **dependency update** across the project, upgrading the `wasm-bindgen` ecosystem to version `0.2.108`. It involves updating the `wasm-bindgen`, `web-sys`, and `js-sys` crate dependencies in the main `Cargo.toml` and the `examples/axum/Cargo.toml`. Crucially, the `wasm-bindgen` Git submodule is also updated, ensuring the project uses the latest `wasm-bindgen` toolchain. This **maintenance** task also updates the internal `worker-build/src/versions.rs` to reflect the new current and minimum required versions for `wasm-bindgen` and `esbuild`, ensuring compatibility and leveraging the latest improvements from these core **WebAssembly build tools**.Jan 156maint
08e538dThis commit significantly **enhances the Continuous Integration (CI) pipeline** by **expanding the test matrix to include Windows environments**, ensuring broader platform compatibility. It also **refactors test execution within `.github/workflows/pullrequest.yml` to leverage `chomp` commands**, centralizing project tasks. This **infrastructure improvement** introduces a new `chompfile.toml` to define and streamline build, lint, format, and test operations, ultimately improving development workflow and test coverage.Dec 292maint
0801465This commit introduces a **maintenance step** within the **GitHub Actions workflow** responsible for creating release pull requests. It adds a new job to **automatically remove local patch references from `Cargo.toml` files** before the release PR is generated. This crucial **pre-release cleanup** ensures that **release builds** are free from development-specific dependency overrides, preventing potential build failures or incorrect dependency resolution in published crates. Ultimately, this **enhances the robustness and correctness of the project's release process**.Dec 201maint
e3010c8This commit performs a significant **dependency update**, upgrading the project's core **`wasm-bindgen` dependency to version 0.2.106**. This involves updating the `wasm-bindgen` git submodule, along with related `js-sys` and `web-sys` crate versions across the main `Cargo.toml` and the `examples/axum` project. Furthermore, the **`worker-build` system** is updated to reflect these new versions by modifying `CUR_WASM_BINDGEN_VERSION` and `MIN_WASM_BINDGEN_LIB_VERSION` constants in `worker-build/src/versions.rs`. A **refactoring** of error messages in `worker-build/src/lockfile.rs` also improves clarity for `cargo_dep_error` when `wasm-bindgen` version mismatches occur, enhancing the overall build experience and ensuring compatibility with the latest `wasm-bindgen` ecosystem.Dec 17maint
d526784This commit **fixes** the **Leptos template** by performing a crucial **dependency update** within its `Cargo.toml` file. Specifically, it updates the `wasm-bindgen` dependency from version `0.2` to `0.2.105` in `templates/leptos/Cargo.toml`. This **maintenance** change ensures that new projects initialized with the **Leptos template** will correctly build and function, preventing potential compilation errors or runtime issues caused by an outdated or incompatible `wasm-bindgen` version.Nov 251–
47f8e1cThis commit **upgrades** the project's **examples** and **templates** to align with the `0.7` release of the `worker` framework. It updates the core `worker`, `worker-macros`, and `worker-sys` dependencies to version `0.7.0` within various `Cargo.toml` files. Additionally, all `wrangler.toml` configurations across the examples and templates are modified to utilize `worker-build` version `^0.7`. This **maintenance** task ensures that all provided starter code and demonstrations are compatible with the latest stable API, preventing potential build or runtime issues for users.Nov 2526maint
914b3dfThis commit **updates the version** of the `worker-build`, `worker-macros`, `worker-sys`, and `worker` crates to `0.7.0`. This **maintenance** task explicitly sets the package versions in their respective `Cargo.toml` files, moving away from workspace inheritance for this release. The change signifies a **new release point** for these core components, making `0.7.0` the official version available for downstream projects.Nov 255–
a11c95bThis commit introduces **deprecations** for various features and APIs in preparation for the upcoming 0.7 release, signaling their eventual removal or significant modification. It primarily affects **public-facing interfaces** and **internal utility functions** that are being phased out, guiding developers towards more current and stable alternatives. This work is a crucial **maintenance** step, ensuring the project's API surface remains clean and consistent as it evolves. The changes facilitate **API evolution**, requiring users of the deprecated functionalities to update their code to align with future standards and avoid breaking changes.Nov 253–
e121075This commit performs **maintenance** by addressing **0.7 deprecations** and applying `clippy` fixes to improve code quality. The primary deprecation handling involves **removing the `worker-kv` crate** from the workspace and dependencies in `Cargo.toml`, streamlining the project's dependency graph. Further **refactoring** includes reordering and simplifying import statements in `examples/kv/src/lib.rs` to reflect direct `KvError` availability from the main `worker` crate. Additionally, the `worker-build` module's `lockfile.rs` receives a **style improvement** by simplifying error mapping in the `get_package_version` method, enhancing overall code readability.Nov 258maint
f6cdab2Mar 25

This commit introduces **support for source phase imports** within **Wrangler**, enabling developers to use the `import source` syntax for advanced module loading. It configures `esbuild` to recognize this syntax, ensuring that **WASM modules imported via `import source` are correctly processed**, copied to the output, and included in the worker bundle, even when `--no-bundle` is specified. This **new capability** also improves **Wrangler's worker format detection**, accurately identifying the 'modules' format when source phase imports are present. Overall, this **enhances Wrangler's bundling and deployment logic**, providing more robust handling for modern JavaScript module patterns.

5 filesgrow
5602399Feb 25

This commit introduces a **robust build locking mechanism** within the **`worker-build` subsystem** to prevent concurrent build processes from corrupting shared output files. It implements a new `BuildLock` that directs all build output into a temporary staging directory (`build/.tmp/`) and uses an mtime-based heartbeat to coordinate and wait for other active builds. This **bug fix** addresses a critical concurrency issue by ensuring that `wrangler`'s worker builds are atomic. The change significantly enhances the **reliability and stability** of worker deployments by preventing build failures and inconsistent states when multiple commands trigger builds simultaneously.

10 fileswaste
4c30cd5Feb 25

This commit **introduces a comprehensive performance benchmarking suite** for the `workers-rs` project, establishing a **new capability** for continuous performance monitoring. It adds a dedicated `benchmark/` module containing Rust worker code (`benchmark/src/lib.rs`) for testing streaming and parallel sub-requests, along with Node.js scripts (`benchmark/run.js`, `benchmark/codspeed-convert.js`) to execute benchmarks against a worker server using Miniflare and convert results for CodSpeed. A new **GitHub Actions workflow** (`.github/workflows/codspeed.yml`) is also integrated to automate benchmark runs on push and pull requests, providing crucial insights into performance regressions and improvements for `workers-rs` applications. This suite allows developers to easily run and analyze performance metrics locally and within CI.

11 filesgrow
73d1b8cFeb 24

This commit performs a **dependency update** for the `wasm-bindgen` toolchain, upgrading it to version `0.2.113`. This **maintenance** task involves updating the `Cargo.toml` file to reflect the new dependency version and synchronizing the `wasm-bindgen` Git submodule reference. The change ensures the project benefits from the latest features, bug fixes, and performance improvements within the **WebAssembly build process** and its Rust-to-JavaScript bindings.

3 files–
0e08d09Feb 24

This commit performs a **dependency update** for the **WebAssembly (Wasm) binding generation** toolchain, advancing `wasm-bindgen` and its related crates to version `0.2.112`. This **maintenance** task updates the `Cargo.toml` dependencies and the `wasm-bindgen` git submodule, ensuring the project utilizes the latest features and bug fixes from the `wasm-bindgen` ecosystem. Additionally, the `LATEST_WASM_BINDGEN_VERSION` constant in `worker-build/src/versions.rs` is updated to reflect this new baseline. This upgrade improves the overall stability and capabilities of **Rust-to-Wasm compilation and JavaScript interoperability**.

3 filesmaint
08f9876Feb 24

This commit delivers a **bug fix** and **refactoring** for the **`SecretStore`** module, resolving issues where `SecretStore::get()` could incorrectly return `None` or silently fail. It **removes an unnecessary `Fetcher` indirection** when constructing `SecretStore` from its JavaScript binding, ensuring the direct use of the binding's `.get()` method for proper method dispatch. Additionally, the commit **stops silently swallowing JavaScript errors** within `SecretStore::get()`, instead propagating them via `Result` to improve error visibility and reliability, aligning its behavior with the `Storage::get` pattern. This change significantly enhances the **runtime stability** and **predictability** of secret retrieval operations.

2 fileswaste
29530cdFeb 21

This commit primarily **updates the `wasm-bindgen` dependency** to version 0.2.110, alongside `web-sys` and the Rust toolchain, as a **maintenance** task. It also includes significant **refactoring** across various modules. Specifically, it standardizes string formatting for error messages and debug output in `test`, `worker-build`, and `worker-macros` components. Furthermore, it enhances the robustness of the **`worker` runtime** by updating `Closure` usage to unwind-safe variants like `Closure::wrap_assert_unwind_safe` in `Delay`, `DurableObject`, and `WebSocket` implementations.

20 filesmaint
5f06bb0Jan 23

This commit introduces **support for the `--panic-unwind` build option** for `worker-build`, enabling Rust panics within **Cloudflare Workers** to unwind rather than immediately aborting. This **new capability** involves updating the `worker-macros` and `worker` crates to wrap critical futures with `AssertUnwindSafe`, ensuring proper panic propagation and recovery in modules like `durable_object`, `event` handlers, and `wait_until` calls. The build process now conditionally inserts `criticalError` logic into the JavaScript shim, and comprehensive **testing infrastructure** has been added to validate unwind behavior. This significantly enhances the robustness and error handling capabilities of Rust-based Workers by allowing for more graceful panic recovery.

17 filesgrow
70fed58Jan 20

This commit **updates the Rust toolchain** configuration for the project, specifically upgrading the channel from version `1.83.0` to `1.87.0` within the `rust-toolchain.toml` file. It also introduces a default profile for the toolchain, standardizing its usage. This is a **maintenance update** to the **Continuous Integration (CI)** infrastructure, addressing potential compatibility issues or preparing for new features. The change ensures the project builds and tests against a more recent and potentially more stable Rust version, thereby improving **build reliability** and **developer consistency**.

1 filesmaint
fd7bf46Jan 20

This commit **updates the project documentation** by removing an outdated reference to `utils::set_panic_hook()` from the example code within `README.md`. It also **deletes the associated 'Caveats' section**, which is no longer relevant to the current project state. This **documentation fix** ensures that users are presented with accurate and current information, preventing confusion when setting up panic handling. The change primarily impacts the **readability and correctness of the `README.md`**, improving the initial user experience by removing deprecated instructions.

1 filesmaint
c92654dJan 15

This commit introduces a **new feature** to the **`worker-build`** system, enabling support for older `wasm-bindgen` versions. It **refactors** the `WasmBindgen` struct in `worker-build/src/binary.rs` to dynamically accept a version string, allowing projects to specify and use older `wasm-bindgen` versions. To facilitate this, the `Cargo.toml` was updated to downgrade `wasm-bindgen` dependencies, and version constants in `worker-build/src/versions.rs` were adjusted. Additionally, the `check_dependency_version` function in `worker-build/src/lockfile.rs` was updated to return the actual version found, improving the robustness of dependency checks. This change significantly improves compatibility and flexibility for projects that rely on specific or older `wasm-bindgen` toolchains.

5 filesmaint
2b5844fJan 15

This commit performs a **dependency update** across the project, upgrading the `wasm-bindgen` ecosystem to version `0.2.108`. It involves updating the `wasm-bindgen`, `web-sys`, and `js-sys` crate dependencies in the main `Cargo.toml` and the `examples/axum/Cargo.toml`. Crucially, the `wasm-bindgen` Git submodule is also updated, ensuring the project uses the latest `wasm-bindgen` toolchain. This **maintenance** task also updates the internal `worker-build/src/versions.rs` to reflect the new current and minimum required versions for `wasm-bindgen` and `esbuild`, ensuring compatibility and leveraging the latest improvements from these core **WebAssembly build tools**.

6 filesmaint
08e538dDec 29

This commit significantly **enhances the Continuous Integration (CI) pipeline** by **expanding the test matrix to include Windows environments**, ensuring broader platform compatibility. It also **refactors test execution within `.github/workflows/pullrequest.yml` to leverage `chomp` commands**, centralizing project tasks. This **infrastructure improvement** introduces a new `chompfile.toml` to define and streamline build, lint, format, and test operations, ultimately improving development workflow and test coverage.

2 filesmaint
0801465Dec 20

This commit introduces a **maintenance step** within the **GitHub Actions workflow** responsible for creating release pull requests. It adds a new job to **automatically remove local patch references from `Cargo.toml` files** before the release PR is generated. This crucial **pre-release cleanup** ensures that **release builds** are free from development-specific dependency overrides, preventing potential build failures or incorrect dependency resolution in published crates. Ultimately, this **enhances the robustness and correctness of the project's release process**.

1 filesmaint
e3010c8Dec 1

This commit performs a significant **dependency update**, upgrading the project's core **`wasm-bindgen` dependency to version 0.2.106**. This involves updating the `wasm-bindgen` git submodule, along with related `js-sys` and `web-sys` crate versions across the main `Cargo.toml` and the `examples/axum` project. Furthermore, the **`worker-build` system** is updated to reflect these new versions by modifying `CUR_WASM_BINDGEN_VERSION` and `MIN_WASM_BINDGEN_LIB_VERSION` constants in `worker-build/src/versions.rs`. A **refactoring** of error messages in `worker-build/src/lockfile.rs` also improves clarity for `cargo_dep_error` when `wasm-bindgen` version mismatches occur, enhancing the overall build experience and ensuring compatibility with the latest `wasm-bindgen` ecosystem.

7 filesmaint
d526784Nov 25

This commit **fixes** the **Leptos template** by performing a crucial **dependency update** within its `Cargo.toml` file. Specifically, it updates the `wasm-bindgen` dependency from version `0.2` to `0.2.105` in `templates/leptos/Cargo.toml`. This **maintenance** change ensures that new projects initialized with the **Leptos template** will correctly build and function, preventing potential compilation errors or runtime issues caused by an outdated or incompatible `wasm-bindgen` version.

1 files–
47f8e1cNov 25

This commit **upgrades** the project's **examples** and **templates** to align with the `0.7` release of the `worker` framework. It updates the core `worker`, `worker-macros`, and `worker-sys` dependencies to version `0.7.0` within various `Cargo.toml` files. Additionally, all `wrangler.toml` configurations across the examples and templates are modified to utilize `worker-build` version `^0.7`. This **maintenance** task ensures that all provided starter code and demonstrations are compatible with the latest stable API, preventing potential build or runtime issues for users.

26 filesmaint
914b3dfNov 25

This commit **updates the version** of the `worker-build`, `worker-macros`, `worker-sys`, and `worker` crates to `0.7.0`. This **maintenance** task explicitly sets the package versions in their respective `Cargo.toml` files, moving away from workspace inheritance for this release. The change signifies a **new release point** for these core components, making `0.7.0` the official version available for downstream projects.

5 files–
a11c95bNov 25

This commit introduces **deprecations** for various features and APIs in preparation for the upcoming 0.7 release, signaling their eventual removal or significant modification. It primarily affects **public-facing interfaces** and **internal utility functions** that are being phased out, guiding developers towards more current and stable alternatives. This work is a crucial **maintenance** step, ensuring the project's API surface remains clean and consistent as it evolves. The changes facilitate **API evolution**, requiring users of the deprecated functionalities to update their code to align with future standards and avoid breaking changes.

3 files–
e121075Nov 25

This commit performs **maintenance** by addressing **0.7 deprecations** and applying `clippy` fixes to improve code quality. The primary deprecation handling involves **removing the `worker-kv` crate** from the workspace and dependencies in `Cargo.toml`, streamlining the project's dependency graph. Further **refactoring** includes reordering and simplifying import statements in `examples/kv/src/lib.rs` to reflect direct `KvError` availability from the main `worker` crate. Additionally, the `worker-build` module's `lockfile.rs` receives a **style improvement** by simplifying error mapping in the `get_package_version` method, enhancing overall code readability.

8 filesmaint

Work Patterns

Beta

Commit activity distribution by hour and day of week. Shows when this developer is most active.

Collaboration

Beta

Developers who frequently work on the same files and symbols. Higher score means stronger code collaboration.

NavigaraNavigara
OrganizationsDistributionCompareResearch