Weekly GitHub Report for Node

Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

---

Table of Contents

• I. News
  • 1.1. Recent Version Releases
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

The current version of this repository is v23.10.0

1.2 Version Information:

Released on March 13, 2025, this version introduces the --experimental-config-file feature, allowing developers to use JSON configuration files like node.config.json to simplify running tests and managing numerous flags, enhancing developer experience. Additionally, it includes updates to root certificates, new TLS and V8 methods, improved error handling, and various dependency and documentation enhancements.

II. Issues

2.1 Top 5 Active Issues:

We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.

1. allocUnsafe is useless since 24: This issue discusses a significant change in Node.js starting from version 24.0.0 where Buffer.allocUnsafe no longer returns uninitialized memory but instead returns zero-filled buffers, effectively making it behave like Buffer.alloc in terms of security but losing its original performance advantage. The discussion centers on whether to fix allocUnsafe to restore its unsafe, faster behavior, replace all usages with alloc to simplify the API, or keep the zero-filling behavior due to security and ecosystem impact concerns, especially since many existing packages and internal dependencies rely on the zero-filled behavior introduced in Node.js 24 and 25.

   • The comment thread extensively debates the trade-offs between performance and security implications of the zero-filling change in allocUnsafe, with contributors analyzing internal code, ecosystem usage (notably in popular packages like tar and chardet), and the risk of introducing security vulnerabilities due to assumptions about buffer contents. Various options are proposed, including reverting the change, adding flags to control zero-filling, or improving documentation to discourage unsafe usage. The discussion also covers release timing, messaging, and the need for clear communication to the ecosystem, with some advocating for backporting fixes to Node.js 24 LTS and others emphasizing adherence to release policies and the complexity of the issue.
   • Number of comments this week: 85

2. maximum Set size in Node 24 vs Node 23. 16M vs 8M: This issue reports a discrepancy in the maximum size of a Set object between Node.js versions 23, 24, and 25, where Node 24 exhibits a maximum Set size roughly half that of Node 23 and 25. The user demonstrates this behavior with a test script adding billions of items to a Set, showing consistent reproduction and expecting uniform maximum sizes across versions.

   • The comments identify the problem as a V8 engine bug affecting Array, Set, and Map maximum sizes, which was introduced in Node 24.0.0 and fixed upstream in Node 25. The discussion confirms the issue matches a previously reported bug, suggests merging related issues, and verifies that applying the upstream fix restores the maximum sizes to expected values in pre-release versions.
   • Number of comments this week: 5

3. mock.property(): 'process.env' does not accept an accessor(getter/setter) descriptor: This issue reports a problem with the mock.property() method when used to mock process.env properties, specifically that process.env does not accept accessor descriptors (getters/setters), causing a TypeError. The user demonstrates that attempting to mock process.env.PATH results in an error due to the underlying design of process.env property descriptors, and questions whether this behavior should be reconsidered.

   • The discussion includes a request to work on the issue and clarification that issues are not typically assigned but contributions via pull requests are welcome. A reviewer is asked to review the submitted PR, and a maintainer explains that the behavior is a deliberate design decision referencing a previous change, suggesting the issue may be closed as WONTFIX unless new motivations arise.
   • Number of comments this week: 5

4. readline/promises.question ignores after the first line, fed with several lines at once: This issue reports a problem with the readline/promises.question method in Node.js where it ignores all input lines after the first when multiple lines are fed at once, causing subsequent inputs to be dropped unexpectedly. The user provides a minimal reproduction involving a parent process sending multiple lines to a child process using readline/promises.question, demonstrating that only the first line is processed while the rest are lost, which complicates building REPL-like programs that rely on this API.

   • The comments discuss a workaround using the event-based readline API instead of the promises API to handle multiple input lines correctly, and question the expected behavior by suggesting that input sent before a prompt may be discarded by design. Another comment compares this behavior to a shell script example where input is buffered even during sleep, highlighting a difference in how input buffering works in readline/promises.
   • Number of comments this week: 3

5. OutgoingHttpHeaders location is officially allowed to be undefined but can't be undefined: This issue addresses a discrepancy in Node.js where the location HTTP header is officially allowed to be undefined according to its type definition, but setting it explicitly to undefined results in a runtime error. The reporter highlights that while the absence of the location header is valid, explicitly assigning it an undefined value causes a TypeError, which seems inconsistent with the expected behavior.

   • The comments clarify that this behavior is intentional and documented in Node.js, where setting a header value to undefined throws an error, distinguishing between a missing property and one explicitly set to undefined. It is suggested that this is more of a type definition issue in the @types/node package rather than a bug in Node.js itself, and the issue has been noted in the DefinitelyTyped repository.
   • Number of comments this week: 2

2.2 Top 5 Stale Issues:

We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.

1. Flaky GC-related tests with V8 12.2: This issue addresses flaky garbage collection-related tests that have become unreliable with the update to V8 version 12.2, specifically mentioning tests like test-shadow-realm-gc-module, test-shadow-realm-gc, and test-net-write-fully-async-hex-string. The proposed approach is to skip these tests temporarily due to their instability caused by changes in V8's garbage collection strategy, while acknowledging that current alternative methods to verify garbage collection may invalidate the tests, and a better testing solution needs to be developed in the future.
2. Flaky test-worker-arraybuffer-zerofill with V8 12.2: This issue concerns the flaky behavior of the test-worker-arraybuffer-zerofill test when running with V8 version 12.2, where the test intermittently fails due to a timeout after approximately 300 seconds. The problem may stem from either a genuine bug or broken timing assumptions causing lost messages, and the current approach is to mark the test as flaky while adding additional logging to aid in debugging.
3. Support loading dynamic addon modules (.node files) when embedding the Node.js shared library without needing to link with node.def: This issue addresses the challenge of loading dynamic Node.js addon modules (.node files) on Windows when Node.js is embedded as a shared library, without requiring the embedding executable to link against the node.def file to reexport necessary symbols. The proposed feature suggests modifying the delay load hook to optionally use an environment variable to locate the Node.js shared library module handle, enabling addon modules to load correctly in embedded scenarios, though potential security concerns remain to be evaluated.
4. Please make Node.js embeddable (e.g. libnode): This issue requests the creation of an embeddable version of Node.js, such as a libnode library, to allow projects to integrate the Node.js runtime and standard library directly within other host environments, like Rust-based applications. The proposer highlights that current solutions are inadequate for embedding Node.js, leading developers to use alternatives like Deno, which lack full compatibility, and emphasizes the potential benefits for various projects and organizations if Node.js provided official support for embedding.
5. unable to sign with external OpenSSL engine after usage of crypto.hash: This issue describes a problem where signing data with an external OpenSSL engine (specifically the gost-engine) fails after using the crypto.createHash function in Node.js version 21.7.0 and later. The user reports that while the signature operation works correctly in version 21.6.2 and earlier, it now throws an "unsupported" error related to digital envelope routines, indicating a regression likely caused by recent changes in the Node.js crypto subsystem.

2.3 Open Issues

This section lists, groups, and then summarizes issues that were created within the last week in the repository.

Issues Opened This Week: 19

Summarized Issues:

• Buffer.allocUnsafe behavior change: Since Node.js v24.0.0, Buffer.allocUnsafe no longer provides a performance benefit over Buffer.alloc because it always returns zero-filled buffers, breaking its original unsafe behavior. This change raises security, performance, and ecosystem compatibility concerns, prompting calls to either fix or deprecate allocUnsafe.
• issues/60423

• Stream and ServerResponse event issues: The drain event on ServerResponse streams is unreliable and sometimes fails to fire after using cork/uncork, causing code that waits for this event to hang intermittently on macOS and consistently on Linux. This suggests a problem with managing writableNeedDrain alongside chunk merging behavior unique to ServerResponse.
• issues/60432

• Child process execFileSync regression on Windows: In Node.js v22.20.0, child_process.execFileSync() fails with an EISDIR error when executing binaries from very long Windows paths using the \\?\ prefix. This causes an illegal operation on the directory 'C:' during internal module resolution.
• issues/60435

• REPL paste garbling issue: Pasting text into a non-last cursor position in the Node.js REPL results in garbled strings, such as displaying {}Noedinstead of{Node}`. This regression affects the prompt's correct rendering of pasted input.
• issues/60446

• Segmentation fault in sqlite subsystem: Using SQLTagStore without maintaining a reference to the underlying DatabaseSync database causes a segmentation fault during insert operations. This crash results from premature garbage collection of the database object.
• issues/60448

• Crash on overriding Object.prototype.get in vm context: Overriding Object.prototype.get with a non-function value inside a Node.js vm context causes a fatal V8 error due to an invalid property descriptor. This leads to a consistent crash when the override is applied.
• issues/60451

• Missing Resolver instantiation in node:stream docs: The node:stream documentation lacks the instantiation of the Resolver object, causing a ReferenceError when example code uses resolver.resolve4. Adding const resolver = new Resolver(); is suggested to fix this issue.
• issues/60455

• Memory leak with socket.destroySoon: In Node.js v22.11.0, repeatedly calling socket.destroySoon on a socket attempting to connect causes multiple EventEmitter listeners to be added. This leads to exceeding the maximum listener limit and triggers MaxListenersExceededWarning errors.
• issues/60456

• Set size regression in Node.js v24: Node.js v24 reduces the maximum size of a Set to about 8 million items, half the size supported in versions 23 and 25. This regression is likely due to a V8 engine bug affecting Set, Map, and Array capacities, which was fixed upstream and restored in Node 25.
• issues/60461

• util.inspect line break regression in v25: In Node.js v25.x, util.inspect() incorrectly inserts line breaks when both breakLength and depth options are set to Infinity, causing multiline output instead of a single line. This behavior is a regression from v24.x.
• issues/60475

• mock.property failure on process.env: The mock.property() method fails to mock process.env properties because process.env does not accept accessor descriptors, resulting in a TypeError when attempting to define such properties.
• issues/60486

• Test hangs on AIX due to memory issues: The addons/stringbytes-external-exceed-max tests intermittently hang on AIX systems instead of being skipped due to insufficient memory. This likely occurs because the expected process.exit() call from common.skip() does not happen, causing test flakiness.
• issues/60494

• Worker_threads URL cloning error: Example code in the Node.js worker_threads documentation throws a DataCloneError when posting a URL through a MessageChannel, as the URL object cannot be cloned. This causes the example to fail instead of printing an empty object.
• issues/60504

• Readline module regression causing ERR_USE_AFTER_CLOSE: Since Node.js v24.2.0, using readline with large input causes an ERR_USE_AFTER_CLOSE error due to the interface being closed prematurely during asynchronous iteration.
• issues/60507

• ESM import failure for CommonJS exports: The raknet-native package's CommonJS exports are not accessible using ESM import syntax, resulting in the imported Client being undefined despite proper exports in index.js.
• issues/60508

• mock.timers does not simulate AbortSignal.timeout: The mock.timers utility fails to properly simulate the AbortSignal.timeout behavior, causing tests relying on abort signals triggered by timeouts to fail because the mock timer does not advance the abort signal as expected.
• issues/60509

• Proposal for custom module import attributes: A proposal suggests allowing custom module import attributes in Node.js to enable bundlers to handle imports differently without causing runtime errors. Currently, unsupported import attributes throw errors or can be inconsistently bypassed.
• issues/60516

• Contributor nomination for collaborator status: The contributor Renegade334 is proposed for nomination as a Node.js collaborator due to sustained activity and contributions, which would facilitate merging their changes.
• issues/60536

• timingSafeEqual crashes on non-Buffer inputs: The timingSafeEqual function crashes the process when receiving non-Buffer inputs after multiple invalid calls, affecting Node.js versions 24.x and 25.x.
• issues/60537

2.4 Closed Issues

This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.

Issues Closed This Week: 9

Summarized Issues:

• Memory Management and Regression: Several issues highlight problems related to memory handling in Node.js, including a significant memory regression in version 24.11.x causing out-of-memory crashes during Playwright tests and a proposal to improve garbage collection by specifying external memory held by objects. These issues indicate ongoing challenges with efficient memory usage and garbage collection prioritization in Node.js.
• [issues/60424, issues/60482]

• Documentation and API Errors: There is a documented error in the SQLite API documentation where a method name was incorrectly referenced, leading to user confusion and errors when calling the non-existent method. This points to the need for accurate and clear documentation to prevent developer issues.
• [issues/60505]

• Update and Asset Management Failures: The automatic update process for ICU version 78.1 failed due to inconsistent asset naming compared to the previous version, causing checksum mismatches and blocking the update. This issue reflects problems in maintaining consistent asset management during updates.
• [issues/60506]

• Module Import Behavior: An issue discusses the inconsistency in attribute validation when a module imports itself, where the validation function does not check import attributes, unlike when importing other modules. This leads to inconsistent behavior and potential confusion in module import handling.
• [issues/60515]

• Security and Device Restoration: A user reported concerns about account hacking and suggested removing all APKs from their Android device to restore it to its original state, highlighting security and recovery concerns. This reflects user-driven solutions to security breaches on devices.
• [issues/60525]

• File System and Package Management: Running 'npm install' deletes custom folders manually added inside the node_modules directory, causing loss of user files. This problem is reproducible and tracked in the npm repository, indicating a critical issue with package management affecting user data integrity.
• [issues/60420]

• Feature Requests for User Experience: There are requests for new features such as implementing a search function in a book catalog to help users find books by title, author, or genre, and a simple web calculator project using HTML and CSS. These issues focus on enhancing user interaction and utility.
• [issues/60442, issues/60449]

2.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.

---

III. Pull Requests

3.1 Open Pull Requests

This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Opened This Week: 54

Key Open Pull Requests

1. [WIP] lib: added logger api in node core: This pull request is a work-in-progress draft that introduces a new logger API into the Node.js core library, including implementation of a flexible API, error serialization, integration with diagnostics_channel, documentation, benchmarks comparing it with the pino logger, and various optimizations and refactorings.

• URL: pull/60468

• Merged: No

• Associated Commits: 7f5db, e149a, 92f68, 2af23, 630e6, 6b775, 04518, 4c781, 091f1, 9a47a, 40f4f, df2b7, 91ae0, 41e33, 99163, f4e10, 7b4e9, d9c51, 40d8b, 239dc, ad2a5, 9c2e2, 11a9b, b216a, 7f45e, f2aa8, f1aba, 5815b, f337c

2. deps: update V8 to 14.3: This pull request updates the V8 JavaScript engine dependency to version 14.3, including necessary patches, build adjustments, and compatibility changes such as updating the NODE_MODULE_VERSION to 144 to accommodate API/ABI changes, while also addressing platform-specific issues and removing deprecated code.

• URL: pull/60488

• Merged: No

• Associated Commits: 15654, 0c141, 32c85, e628e, ff17d, 31abf, e9f3a, a9dcb, 27b69, 98d24, 78940

3. net: do not add multiple connect and finish listeners when multiple Socket.destroySoon's were scheduled: This pull request addresses the issue of multiple connect and finish event listeners being added when multiple Socket.destroySoon calls are scheduled by ensuring that new finish event listeners are only added if they have not been previously attached to the given socket.

• URL: pull/60469

• Merged: No

• Associated Commits: 6e330, 9905c, afe83, 565e2, 94eda, e5ec2, ae573, a70ef, a63fb, 40ef4

Other Open Pull Requests

• Devcontainer configuration update: This pull request restructures the outdated .devcontainer.json into .devcontainer/base/devcontainer.json following GitHub's recommended setup and adds support for both arm64 and amd64 official images to enable automatic selection by devcontainer tools. It also includes new documentation and a screencast demonstrating efficient building and testing of development branches.
  • pull/60472

• Fixes and improvements in Node-API and SharedArrayBuffer support: Multiple pull requests improve Node-API usage by including node_api_types.h instead of node_api.h to reduce API surface, add support for SharedArrayBuffer in napi_create_dataview, and introduce an internal binding to construct SharedArrayBuffers via the V8 API for more reliable creation independent of runtime flags. These changes prevent errors and improve modularity and safety in SharedArrayBuffer handling.
  • pull/60473, pull/60496, pull/60497

• Test suite assertion reachability improvements: Several pull requests aim to enhance test reliability and coverage by ensuring assertions are reachable in various test suites, including test/internet and test/es-module. These changes improve the robustness of the testing framework and serve as follow-ups to related prior work.
  • pull/60513, pull/60485, pull/60498, pull/60501

• Stream module enhancements: Pull requests add a bytes() method to the stream/consumers module returning a Uint8Array for convenient typed array consumption, propose a new Readable.readv method as a faster alternative to Readable.read, and optimize readable streams to return one buffer at a time instead of concatenating multiple buffers, reducing CPU usage. These changes improve stream usability and performance.
  • pull/60426, pull/60439, pull/60440, pull/60441

• Bug fixes related to event handling and environment mocking: Fixes include resolving an event listener leak in the debugger's run command by properly removing listeners on error or ready events, and correcting a TypeError in node:test by modifying mock.property() to assign values directly when mocking process.env. These fixes prevent memory leaks and ensure safe environment variable mocking.
  • pull/60464, pull/60499

• Performance optimizations: Pull requests optimize console logging for single-string inputs by adding a fast path and reducing method calls, and improve package configuration caching by storing both existing and missing package.json files to avoid redundant filesystem calls. These changes significantly enhance performance in logging and package resolution.
  • pull/60422, pull/60425

• Path resolution and platform compatibility fixes: Fixes include resolving an EISDIR error on Windows by validating and adjusting drive-letter-only paths before calling fs.realpathSync(), and improving OpenSSL x86 assembly build compatibility on win32 and other x86 architectures by conditionally using nasm-style or gcc-style preprocessor syntax. These changes enhance cross-platform stability.
  • pull/60438, pull/60510

• Memory leak and heap statistics improvements: One pull request fixes a memory leak in the TLS module caused by invalid secureProtocol validation preventing cleanup, while another backports a V8 commit adding a total_allocated_bytes() method to the HeapStatistics API for tracking all heap allocations since Isolate creation. These address memory management and diagnostics.
  • pull/60427, pull/60429

• Documentation fixes: A pull request corrects the perf_hooks documentation by fixing examples to properly use the performance object for eventLoopUtilization() and adds a clarifying note about method access. This improves clarity and correctness of the documentation.
  • pull/60421

3.2 Closed Pull Requests

This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Closed This Week: 28

Key Closed Pull Requests

1. src: fix timing of snapshot serialize callback: This pull request addresses the issue of improper timing for the addAfterUserSerializeCallback() during the built-in snapshot creation in Node.js by initializing these callbacks when lib/internal/v8/start_snapshot.js is loaded, ensuring they run correctly, and adds an internal usage counter in debug builds to verify the callback path during snapshot building.

• URL: pull/60434

• Merged: No

• Associated Commits: 0f2ec, 454ca, 998b0, d6d46

2. test: skip failing test on macOS 15.7+: This pull request addresses an issue caused by updated GitHub Actions runners on macOS 15.7+ by skipping a failing test to unblock other pull requests from landing.

• URL: pull/60419

• Merged: Yes

• Associated Commits: d7d72, 3303b

3. tools: pin OpenSSL to 3.5.4 on test-shared workflow: This pull request pins the OpenSSL version to 3.5.4 in the test-shared workflow to work around issues with OpenSSL 3.6.0, adds the cachix/cachix-action to avoid rebuilding OpenSSL on every run, and ensures secure caching for pull requests from forks.

• URL: pull/60428

• Merged: Yes

• Associated Commits: 3d78c, 6cc35

Other Closed Pull Requests

• Test and CI stability fixes: Multiple pull requests address flaky tests and improve debugging in continuous integration environments. These include fixing a flaky watch mode kill signal test by limiting writes to prevent infinite loops and enhancing debugger tests by capturing stack traces on timeouts to better diagnose failures.
  [pull/60443, pull/60457]

• Linter and release proposal improvements: Several pull requests fix and improve the release-proposal linter to handle Long-Term Support (LTS) transitions and semver-major release proposals correctly. These changes prevent failures by adjusting expectations for commits and changelog entries during release processes.
  [pull/60465, pull/60481]

• Documentation updates: Multiple pull requests add or clarify documentation, including adding a known issue to the v24.11.0 release notes, clarifying Linux runtime requirements for Node.js 25+ regarding libatomic, updating perf_hooks examples, and fixing SQLite StatementSync documentation.
  [pull/60467, pull/60484, pull/60445, pull/60474]

• Long Term Support (LTS) release management: One pull request marks Node.js v24.11.0 "Krypton" as entering LTS, updating metadata and establishing support through April 2028 without other changes from v24.10.0.
  [pull/60414]

• Dependency and memory safety fixes: A pull request patches npm and tar dependencies to avoid returning uninitialized memory by forcing .alloc usage instead of .allocUnsafe as a temporary fix before upstream updates.
  [pull/60430]

• Testing workflow optimizations: One pull request improves test efficiency by skipping the test-shared.yml suite when only dependency folders change, avoiding unnecessary test runs.
  [pull/60433]

• Web Platform Tests (WPT) stability: A pull request removes undici WPT from daily wpt.fyi jobs to fix failures caused by fixture location changes, restoring stable daily Node.js WPT report uploads.
  [pull/60444]

• Stream and performance improvements: Pull requests improve the stream module by preventing redundant reads during ongoing operations and add diagnostics channels to HTTP/2 client stream request bodies and readable streams for better inspection and tracking without side effects.
  [pull/60454, pull/60480, pull/60514]

• Code cleanup and alignment: One pull request cleans up the generic counter implementation by addressing review comments and aligning with existing V8 fast call counters.
  [pull/60447]

• Node.js inspect utility styling fix: A pull request fixes styling of special properties in the inspect utility to stylize only keys, keeping colons and spaces unstyled for consistent output formatting.
  [pull/60479]

• TypeScript support proposal: A pull request proposes enabling TypeScript sources in core modules with type checking by stripping .ts files at build time, allowing gradual migration and potential shipping of native types.
  [pull/60489]

• Test compatibility fixes: One pull request skips deprecated legacy buffer write tests for Node.js v18+ to maintain test stability and successful CI runs without changing core functionality.
  [pull/60493]

• Tooling updates: A pull request adds documentation indicating nixpkgs updates should not be backported, and another fixes the update-icu script addressing a reported issue.
  [pull/60431, pull/60521]

• Unmerged proposals: Several pull requests propose updates to async_resource.cc, README.md, and library code optimizations that were not merged.
  [pull/60460, pull/60478, pull/60522]

3.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.

---

IV. Contributors

4.1 Contributors

Active Contributors:

We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.

If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.

Contributor	Commits	Pull Requests	Issues	Comments
joyeecheung	50	21	3	47
aduh95	43	25	1	41
ChALkeR	5	5	6	66
mertcanaltin	31	1	0	21
Renegade334	10	8	4	14
targos	24	3	2	7
legendecas	18	4	0	13
addaleax	12	4	0	15
richardlau	4	3	1	17
gurgunday	13	7	0	2