gchq/CyberChef - Open Source PR Review Scorecard

The Cyber Swiss Army Knife - a web app for encryption, encoding, compression and data analysis

C-Rank Grade: A (Welcoming) - 56/100

External PR Merge Rate: 40%

Response Time: 2d

First Timer Success: 35%

Frequently Asked Questions

Is gchq/CyberChef welcoming to first-time open-source contributors?

gchq/CyberChef has a recorded first-timer success rate of 35.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in gchq/CyberChef respond to incoming external pull requests in approximately 36.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 55.9 C-Rank™ score (A Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 55.9 places gchq/CyberChef in the A tier.

What is the external contributor pull request merge rate for gchq/CyberChef?

The external contributor pull request merge rate for gchq/CyberChef is 40.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in gchq/CyberChef?

gchq/CyberChef currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

gchq
gchq/CyberChefA•Welcoming36.1k
GitHub
Back to Explorer
gchq

gchq/CyberChef

36,063
InactiveA•Welcoming(56/100)JavaScript

The Cyber Swiss Army Knife - a web app for encryption, encoding, compression and data analysis

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
5.0/10
Patience Score
6.0/10
Nitpick Rate
65%

Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in gchq/CyberChef.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Run repository linter and code formatters locally before pushing
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
40.5%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
35.5%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
46 core
Highly collaborative maintainer core
Diagnostic Health HUD
40.5%
Merge Gauge
35.5%
1st-Timer
Community Vibe29/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for gchq/CyberChef
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/gchq/CyberChef)](https://getmerged.abhishekco.de/gchq/CyberChef?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Describe the bug For webpack up to and including 5.109.2 "npm run build" produces a working build. If webpack 5.110.0 (or later) is installed the build fails. Tweaking the config to set stats.children to true gives the following errors: ... ERROR in InputWorker.js InputWorker.js from Terser plugin Unexpected token: punc (;) [InputWorker.js:16530,undefined] at js_error (/workspaces/CyberChef/node_modules/terser/dist/bundle.min.js:577:11) ... Child worker-loader /workspaces/CyberChef/node_modules/babel-loader/lib/index.js??ruleSet[1].rules[0]!/workspaces/CyberChef/src/web/workers/InputWorker.mjs compiled with 1 error ... ERROR in ZipWorker.js ZipWorker.js from Terser plugin Unexpected token: punc (;) [ZipWorker.js:25064,undefined] at js_error (/workspaces/CyberChef/node_modules/terser/dist/bundle.min.js:577:11) ... To Reproduce Steps to reproduce the behaviour or a link to the recipe / input used to cause the bug: "npm install --save-dev [email protected] "npm run build" Expected behavio

📅 Opened Sep 6, 2026💬 0 comments
Quality: 50/100Contribute

The test here is flaky and is failing about 30% of the time particularly in the Node 26 build. The test times out at line 184. CyberChef/tests/browser/01_io.js Lines 170 to 184 in bf244e9 "Autobaking the latest input": browser => { // Use the sleep recipe to simulate a long running task utils.loadRecipe(browser, "Sleep", "input", [2000]); browser.waitForElementVisible("#stale-indicator"); // Enable previously disabled autobake browser.expect.element("#auto-bake").to.not.be.selected; browser.click("#auto-bake-label");

📅 Opened Sep 6, 2026💬 0 comments
Quality: 50/100Contribute

The current tool provides complete and excellent core functions with stable performance and user-friendly interaction. It greatly improves the efficiency of daily AUTOSAR development and security configuration work, and has been very helpful for our routine development tasks. To further improve the tool’s integration and meet the standard requirements of automotive hardware security development, we propose adding a built-in SHE key generation function in accordance with the official AUTOSAR specification. The relevant design shall refer to the document: https://www.autosar.org/fileadmin/standards/R25-11/FO/AUTOSAR_FO_TR_SecureHardwareExtensions.pdf In actual ECU security development, SHE (Secure Hardware Extension) is a critical security module for vehicle MCU encryption. The specification defines multiple standard key slots including MASTER_ECU_KEY, BOOT_MAC_KEY, KEY_1~KEY_10, and RAM_KEY, which correspond to secure boot, data encryption, key update and other security scenarios. At

📅 Opened Jul 20, 2026💬 1 comment
Quality: 40/100Contribute

I cannot write or test YARA-X rules in CyberChef, like using the "with" statement. It is also faster, which will enhance the user experience. Add a YARA-X Operation that uses a webasm module compiled directly from the YARA-X codebase instead of a third party integration. Current Alternatives: Use legacy YARA in CyberChef: This forces analysts to avoid new YARA-X features and maintains slower execution times on large datasets. The legacy YARA operation is not updated regularly. Test with YARA-X locally: Running the YARA-X CLI tool locally against downloaded payloads breaks worflows that CyberChef provides. Use external web testers: Copying payloads to other online YARA testing sandboxes introduces friction and potential operational security (OPSEC) risks if the data is sensitive. YARA-X is the official successor to YARA, built by VirusTotal. Since it is designed with a strong focus on developer experience and modern architecture, the YARA-X project already includes support for WASM bi

📅 Opened Jul 1, 2026💬 2 comments
Quality: 40/100Contribute

To reproduce that extremly very simple, just drag AMF decode then you will see an uncaught error AMF Decode - Error in https://gchq.github.io/CyberChef/modules/Encodings.js on line 2.<br><br>Message: Buffer exhausted while reading 8 bits at offset 0, context: - [ye] Ue#marker - [readField()] Ue#marker - [read()] Ue - [Ue.read()] Ue Direct Test Link: https://gchq.github.io/CyberChef/#recipe=AMF_Decode('AMF3')&oenc=65001&oeol=VT https://gchq.github.io/CyberChef/#recipe=AMF_Decode('AMF3')&input=ChMBA2EFQAg&oenc=65001&oeol=VT https://gchq.github.io/CyberChef/#recipe=AMF_Decode('AMF3')&input=CRMBA2EFQAg&oenc=65001&oeol=VT

📅 Opened Jun 4, 2026💬 2 comments
Quality: 30/100Contribute
Looking for more JavaScript beginner tasks?Explore JavaScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for gchq/CyberChef

When evaluating whether to contribute to gchq/CyberChef, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of gchq/CyberChef acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 40.5% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to gchq/CyberChef

01

Is gchq/CyberChef welcoming to first-time open-source contributors?

gchq/CyberChef has a recorded first-timer success rate of 35.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 55.9 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 55.9 places gchq/CyberChef in the Welcoming tier.

04

What is the external contributor pull request merge rate for gchq/CyberChef?

The external pull request merge rate is 40.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in gchq/CyberChef?

Yes, gchq/CyberChef currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for gchq/CyberChef are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.