Weekly GitHub Report for Node: April 21, 2025 - April 28, 2025 (12:02:42)
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:
The current version of this repository is v23.10.0
1.2 Version Information:
The version released on March 13, 2025, introduces the --experimental-config-file feature, allowing developers to use a JSON configuration file to streamline the use of multiple flags, enhancing the developer experience and potentially increasing adoption. Notable updates include improvements in error handling, updates to root certificates, and the addition of new methods like tls.getCACertificates() and v8.getCppHeapStatistics(), reflecting a trend towards enhancing security, performance, and developer convenience.
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.
-
Integrate OpenTelemetry: This issue discusses the potential integration of OpenTelemetry (OTEL) into Node.js, highlighting its benefits as a vendor-neutral observability standard and its recent adoption by Deno. The proposal suggests that incorporating OTEL could simplify integrations and enhance performance, while also considering the challenges of compatibility and the need for a flexible approach that allows for user customization.
- The comments reflect a robust discussion on the feasibility and implications of integrating OpenTelemetry into Node.js. Participants express concerns about the size and complexity of OTEL, suggesting alternatives like enhancing
diagnostics_channelfor better telemetry support. Some advocate for a separate npm package for OTEL integration, while others emphasize the importance of maintaining flexibility and avoiding direct dependencies in Node.js core. The conversation also touches on the potential for collaboration between OTEL anddiagnostics_channelto create a unified instrumentation API, with a focus on balancing ease of use and performance. - Number of comments this week: 20
- The comments reflect a robust discussion on the feasibility and implications of integrating OpenTelemetry into Node.js. Participants express concerns about the size and complexity of OTEL, suggesting alternatives like enhancing
-
node.config.jsondoesn't respect optionally-valued or aliased options: This issue involves a bug in thenode.config.jsonfile where optionally-valued or aliased options, such as theinspectflag, are not being correctly interpreted when set totrueor other values. The expected behavior is for the configuration to recognizetrueas enabling the flag and other values as specific settings, but instead, it results in errors indicating unknown nodes or invalid content.- The comments discuss the issue with the
inspectoption, which expects a host:port value and throws errors when a boolean is provided. Contributors suggest that the problem lies with the--inspectimplementation rather than the config parser, and there is a proposal to modify the inspector to handle boolean values correctly. A pull request is welcomed to address the issue, and one contributor expresses interest in attempting a fix. - Number of comments this week: 8
- The comments discuss the issue with the
-
Nominating dario-piotrowicz as a collaborator: This issue is about nominating Dario Piotrowicz as a collaborator for the Node.js project, highlighting their active contributions and involvement with the Node.js website team. The nomination is supported by links to Dario's authored commits, opened pull requests, and issues, as well as their comments on pull requests and issues within the Node.js organization.
- The comments section is overwhelmingly positive, with multiple users expressing strong support for Dario's nomination as a collaborator, including several "+1" endorsements and praise for their contributions to the team.
- Number of comments this week: 8
-
Using and editing
vcbuild.batis not as intuitive asMakefile: This issue highlights the challenges faced by a developer who recently transitioned from a Linux to a Windows environment, finding thevcbuild.batscript in the repository less intuitive and more error-prone compared to the Makefile. The developer suggests modernizingvcbuild.bator making the Makefile cross-platform to enhance the development workflow on Windows, and also mentions the potential of using CMake as a cross-platform tool.- The comments discuss various approaches to improve the build system, including making the Makefile work on Windows, exploring CMake, and considering Bazel for its caching and parallelization benefits. Contributors share their experiences and partial implementations, with some expressing a preference for CMake due to its wider adoption. There is also a suggestion to simplify the build process by using Python to manage scripts, inspired by how Bun handles build logic.
- Number of comments this week: 7
-
Make
util.isArray()EOL: This issue discusses the proposal to mark theutil.isArray()method as end-of-life (EOL) in the Node.js project, as it is the last remainingutil.is*type-checking method after others were deprecated in version 23.0.0. The issue raises the question of whether there is any remaining justification for keeping this method, given that its previous use in the form-data library has been removed.- The comments discuss the need to open a pull request and consider the impact on other libraries, suggesting running tests with citgm. There is a willingness to investigate further, but concerns are raised about the continued use of
util.isArray()in third-party dependencies. A suggestion is made to manage and backport changes if the list of affected dependencies is small. - Number of comments this week: 6
- The comments discuss the need to open a pull request and consider the impact on other libraries, suggesting running tests with citgm. There is a willingness to investigate further, but concerns are raised about the continued use of
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.
- Flaky GC-related tests with V8 12.2: This issue concerns flaky garbage collection-related tests in the V8 12.2 engine, specifically involving the
test-shadow-realm-gc-module,test-shadow-realm-gc, andtest-net-write-fully-async-hex-string. The problem seems to stem from incorrect assumptions in the tests that are disrupted by V8's new garbage collection strategy, leading to the suggestion of skipping these tests until a more reliable testing method is developed. - Flaky
test-worker-arraybuffer-zerofillwith V8 12.2: This issue concerns a flaky test namedtest-worker-arraybuffer-zerofillassociated with V8 version 12.2, which has been failing intermittently, as indicated by a timeout error in the console output. The problem might be due to a real bug or broken timing assumptions/messages getting lost, and it has been suggested to mark the test as flaky and add logs for better debugging. - Support loading dynamic addon modules (
.nodefiles) when embedding the Node.js shared library without needing to link withnode.def: This issue addresses the challenge of loading dynamic addon modules, specifically.nodefiles, when embedding the Node.js shared library into a different executable without the need to link withnode.def. The proposed solution suggests modifying the delay load hook to utilize an environment variable, potentially namedNODE_LIBRARY, to facilitate the loading process, although the security implications of this approach are still uncertain. - unable to sign with external OpenSSL engine after usage of crypto.hash: This issue involves a problem with signing using an external OpenSSL engine after utilizing the
crypto.hashfunction in Node.js, specifically affecting versions v21.7.0 and v21.7.1. The error occurs consistently and is believed to be linked to recent changes in the Node.js codebase, as the functionality worked correctly in version v21.6.2 and earlier. Since there were fewer than 5 open issues, all of the open issues have been listed above.
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:
- Node.js Configuration and Bugs: Issues related to Node.js configuration highlight bugs in handling options and arguments, such as the
--inspectflag not being correctly interpreted when a boolean value is provided, leading to errors. Additionally, unused arguments in functions likeOutgoingMessage.prototype._writeRawraise concerns about potential bugs and the need for codebase cleanup.
- Node.js Documentation and Features: Several issues address the need for documentation updates and feature enhancements in Node.js, such as the lack of documentation for the
http.requestfunction's ability to send headers as an array of strings. There is also a proposal to add a--repeat-until-n-failuresflag to the test runner to improve debugging of flaky tests.
- Node.js Error Handling and Deprecation: Discussions around error handling and deprecation include updating the
isErrorutility function to use the newError.isErrormethod, and considering the deprecation ofutil.types.isNativeError. Additionally, there is a proposal to prevent theERR_REQUIRE_ASYNC_MODULEerror from being triggered unnecessarily.
- Node.js Development Environment and Tools: Issues highlight challenges in the development environment, such as the complexity of using
vcbuild.baton Windows compared to Makefile, suggesting modernization or cross-platform solutions. There is also a request for a distributed, statically linked version of Node.js for Docker images to streamline integration.
- Node.js HTTP/2 and Protocol Compliance: A bug in Node.js where HTTP/2 requests with an invalid
:pathheader are not rejected as expected highlights the need for compliance with the HTTP/2 specification. This issue emphasizes the importance of adhering to protocol standards to prevent unexpected behavior.
- Node.js REPL and Customization: Enhancements to the Node.js REPL module are proposed to allow developers to suppress or customize default dot commands in a custom shell-like environment. This would enable the use of these commands within a custom eval function, enhancing security and functionality.
- Node.js Observability and Telemetry: The potential integration of OpenTelemetry into Node.js is discussed to enhance observability, leveraging a vendor-neutral standard to simplify integrations and improve performance. The use of
diagnostics_channelas a foundational API is considered to support various telemetry needs.
- Node.js Garbage Collection and Performance: Implementing events in the V8 module to notify before and after garbage collection is proposed to manage traffic redirection and minimize service outages in Kubernetes environments. This aims to address the ineffectiveness of current methods in detecting memory pressure.
- Node.js Memory Management: A mechanism to detect when the
MemoryCacheStorereaches its maximum size is requested, as there is currently no way to identify when this limit is exceeded. This would improve memory management and prevent potential issues related to cache overflow.
- Node.js API and Method Deprecation: The potential end-of-life for the
util.isArray()method is discussed, questioning its continued use after removal from the form-data library. The impact on third-party dependencies and the need for further testing with the citgm tool are considered.
- Node.js Codebase Refactoring: Refactoring the codebase to replace C-style function pointer definitions with
std::functionis proposed to enhance type safety, readability, and flexibility. This ensures that all instances are updated while maintaining functionality.
- Node.js Global API Proposal: Making
AsyncLocalStoragea global in Node.js is proposed to separate it from theasync_hookAPI and encourage its use. Alternatives such as moving it to its own top-level file or aliasing it to a new built-in module are also considered.
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: 12
Summarized Issues:
- Database Location Retrieval: This issue proposes adding a method
DatabaseSync.prototype.locationto retrieve the database location, which would be useful when only theDatabaseSyncobject is available. It suggests using this method as a wrapper forsqlite3_db_filename, while also considering potential implications for database re-opening and connection parameters.
- Segmentation Fault on x86 with Shared libuv: A segmentation fault occurs on x86 platforms when Node.js is built with a shared libuv library, specifically version 1.46.0. This issue does not occur when using static linking, and the problem is not observed on other architectures like amd64, armhf, or s390x.
- NPM Installation Error Due to Environment Variable: Users are unable to install or use npm due to a misconfigured system environment variable that incorrectly repeats the module path. This causes Node.js to throw a 'MODULE_NOT_FOUND' error, which was resolved by deleting the erroneous path from the environment variables.
- Node.js Timers Documentation Update: The Node.js timers documentation needs updating to clarify that the
setTimeout()andsetInterval()functions return aTimeoutobject. This differs from the numeric timer ID returned in browsers, to prevent confusion among developers who might not be aware of Node-specific methods likeunref().
- Node.js Interactive Shell Freeze on Windows: A bug in Node.js version v22.14.0 on Windows causes the interactive shell to freeze and become unresponsive when typing
while(1)conso. The problem does not occur in earlier versions on Debian and is resolved in version v23.1.0.
- FIPS Mode Error on Windows: An error occurs when attempting to enable FIPS mode in a Node.js application on Windows, resulting in an "SSL routines::library has no ciphers" error during HTTPS requests. This happens despite having configured OpenSSL with the FIPS provider and successfully running the same setup on Linux.
- Clarification Needed for process.nextTick() Documentation: The explanation of output in the example code on the "Understanding process.nextTick()" page is unclear, specifically regarding the execution order of
setImmediateandsetTimeout. A revision is suggested to align with the correct behavior as described in another related document.
- Flakiness of parallel/test-repl-import-referrer Test: The
parallel/test-repl-import-referrertest has been failing due to timeouts on various platforms including Linux x64 and Linux s390x. This flakiness has been linked to recent updates made to the test, causing failures in multiple pull requests.
- Need for Prebuilt libnode Binaries: There is a need for Node.js to officially distribute prebuilt libnode binaries, as currently, embedders must manually compile or rely on unofficial sources. The proposal suggests making these binaries available on the Node.js website to facilitate easier distribution and integration for applications that depend on libnode.
- Explicit Glob Argument in Test Runner: The need for an explicit glob argument in the test runner is discussed to avoid repetitive and error-prone script configurations in
package.json. Improvements such as named arguments or configuration options are suggested to streamline the process.
- Empty GitHub Issues: Some issues, such as "My" and "OnePieceStore," lack further details or discussion since the body is empty and there are no comments.
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: 36
Key Open Pull Requests
1. util: update util.isArray() to eol: This pull request involves updating the util.isArray() function to mark it as end-of-life (eol), addressing issue #58013, and includes several commits that fix typos, update version changes, and modify documentation to reflect the deprecation and removal of references to Array.isArray() in the utility documentation.
- URL: pull/58027
- Merged: No
2. [v22.x backport] src: add config file support: This pull request introduces support for configuration files in the Node.js project, specifically for the v22.x branch, by adding new features such as namespacing config file flags, creating a mechanism to throw errors before bootstrapping, setting a default configuration file named node.config.json, and enhancing test coverage for these changes, as detailed in the associated commits and reviewed by multiple contributors.
- URL: pull/57958
- Merged: No
3. lib: consolidate Channel and ActiveChannel into single class: This pull request aims to merge the Channel and ActiveChannel classes into a single class to avoid dynamically modifying prototypes and reduce duplication, while also replacing underscore-prefixed properties with private properties, with the goal of including these changes in version 24 of the project.
- URL: pull/57977
- Merged: No
Other Open Pull Requests
- SQLite Module Enhancements: This topic covers improvements to the SQLite module in Node.js, including the introduction of benchmarks and a fast API for transaction checking. The benchmarks test various operations like preparing insert statements and executing select queries, while the fast API addition aims to stabilize SQLite but encounters unresolved build errors.
- Build and Compilation Updates: Several pull requests focus on updating build processes and dependencies, such as mandating ClangCL on Windows and updating the sccache version. These changes address issues like test failures and anticipated compilation errors with future V8 updates.
- Deprecation and Removal of APIs: Node.js is moving towards deprecating and removing outdated APIs, such as the
assert.CallTrackerandSlowBuffer. These changes include documentation updates and suggest alternative APIs for better performance and maintainability.
- Enhancements to Error Handling and Diagnostics: Improvements in error handling and diagnostics include replacing certain functions in
exceptions.ccand introducing a diagnostics channel for HTTP/2. These changes aim to enhance integration with network inspector protocols and improve error handling robustness.
- V8 and Performance Improvements: Enhancements in V8 and performance include extending the use of the C++20 ranges library and backporting the
--perf-profflag for macOS. These updates aim to simplify code and enable better profiling capabilities on macOS.
- AsyncLocalStore and Async Context Tracking: Updates to AsyncLocalStore and async context tracking include new tests and marking certain methods as stable. These changes reflect the transition away from async_hooks and aim to reduce confusion for end users.
- HTTP and Network Enhancements: Enhancements in HTTP and network functionalities include the introduction of the
inspector.Network.dataReceivedAPI and updates to thehttp.mddocumentation. These changes aim to improve monitoring of HTTP data chunks and clarify default timeout values.
- REPL and Command Editing Improvements: The Node.js REPL now supports inline multiline editing, enhancing the user experience by allowing users to edit multiline commands as they are written. This feature is currently supported only in TTY environments.
- Import.meta Properties Graduation: The
import.metaproperties, includingimport.meta.resolve(), are proposed to graduate from experimental status. This change is detailed in a specific commit and reflects the maturity of these features in the Node.js project.
- Miscellaneous Enhancements and Fixes: Various other enhancements and fixes include updates to the
isErrorfunction, adjustments for Electron's custom archive formatting, and extraction of theabseiltarget fromv8.gyp. These changes aim to improve functionality and reduce potential issues in the Node.js project.
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: 45
Key Closed Pull Requests
1. 2025-04-15, Version 22.15.0 'Jod' (LTS), @RafaelGSS: This pull request introduces Node.js version 22.15.0 'Jod' (LTS), which includes several notable changes such as implementing partial error comparison and improving partialDeepStrictEqual in the assert module, enhancing performance in assert and util modules, adjusting assert runtimes in benchmarks, allowing --cpu-prof* in NODE_OPTIONS, updating root certificates to NSS 3.108, supporting --use-system-ca on Windows and macOS, adding TLSA record query and parsing in the dns module, implementing synchronous hooks for preparsing in import(cjs), adding execve and threadCpuUsage in the process module, introducing new features in the sqlite module, setting thread names in the src module, adding WPT for URLPattern, implementing tls.getCACertificates(), adding URLPattern implementation, exposing a diff function used by assertion errors, adding v8.getCppHeapStatistics() method, and adding zstd support in the zlib module.
- URL: pull/57840
- Merged: 2025-04-23T07:13:42Z
- Associated Commits: 9ab85, e96f8, d01fd, 5b8bf, b2c3d, 38797, 9897e, ced7d, 4dea5, 41e8f, c76f4, 2a3b5, 8e8b0, 3110e, e78a2, 4f36f, 11505, 848dd, 96c31, 84716, 86e10, 57a1c, ff02a, 84ac1, b7e48, 4b8c6, bda0c, 4b613, c512a, f67ef, 13e5d, 5addb, 11c57, c0364, 4c225, ccf6c, 268db, 5ad0a, 3c8bd, 32702, 143c7, fb151, 32774, a941b, 56fd8, c55e2, 9bc30, 54b4f, ff202, dbabf, e501b, 6fbbf, 277ca, 6bbe2, f2d3a, 8deb5, 33182, 01fc2, c0398, ca510, 4dbf1, 4a30f, 07ea5, f99b6, 6e7f9, 76184, 46e86, acf1a, 4e8a5, af367, 1b4b8, 08dbd, 80d12, 8dbcd, 874de, 52b06, 98733, 0da17, 595a9, 47273, 4f15f, f0495, c694a, 7929a, 66298, 26be8, 4c042, bec15, 54c66, bc863, 4a0ce, db4b0, 3b1f2, 889f8, 26fcf, 7905e, 0974d, 63316, bbe6f, b759a, 6b204, c79fe, 6fe10, 26adc, 16ed8, 5ceb4, 13197, b4fe8, 55996, 7e099, 6eef7, d4601, 1323b, f09fc, c03dd, a9bf3, 969d6, 61e70, fe992, 24327, 89edf, 138cd, bfc75, 2446e, 66b99, 9490c, f49b7, 06070, e59ea, 7cf5d, 1a7f6, de142, 04985, 1ca67, 9d2de, 199a9, 7265b, 4937b, 63d02, 4b8c4, ef64a, 2d1de, 6c4bb, 72504, d343b, 35bb3, f806e, a2215, 7aca2, b94c7, be691, 4adf9, e786e, d52f5, 97856, 39987, b009c, 221dd, ba3cf, 5cea5, 78e48, a2bb6, b3a1c, b2792, 92daa, 68eb1, 8847f, 0c11a, 460f4, bc6fb, 2c974, 09443, 2dfc7, 314b7, b91a8, 5c362, a262a, 3fd63, 1f3fe, 10722, 1688a, 44072, 1ca82, d68b8, 18371, c6efc, 96e3d, 2cd6f, 39e40, 3ab4a, 2cea0, 30e4b, 486d0, ed49f, 4aa03, 4ef79, ea5e8, 40ac5, 60408, 291fb, f74e0, eeb60, fca34, 0a6e7, 936af, 0c5ec, aa588, 47bcc, e4793, c4bf1, eb2dd, 534cc, 548a1, e058b, 7b41d, 7d785, 49f2a, 7bb03, f6941, 82869, 5611f, acd90, f8661, a15e9, d4670, 4b8d6, 2fc13, 10f86, 00eaf, 11961, e6933, 22b89, 3f064, 2dd6d, 4f627, be1f2, e7bea, 7fcb8, 3340d, 16715, 51d02, acffb, 12d39, 6b742, 88075, d39bc, 0ad36, adc70, 097f2, e1372
2. src: use ranges library (C++20) to simplify code: This pull request introduces the C++20 ranges library to simplify a piece of code in the Node.js project, with the primary aim of testing compatibility across platforms, and includes several commits addressing code formatting, such as breaking long lines, adding a missing algorithm header, and performing linting tasks.
- URL: pull/57975
- Merged: 2025-04-25T17:52:42Z
3. test: fix test-repl-import-referrer flakiness: This pull request addresses the flakiness of the test-repl-import-referrer in the Node.js project by implementing a solution that avoids relying on setTimeout, as detailed in the commits co-authored by Luigi Pinca, and aims to resolve issue #58009.
- URL: pull/58014
- Merged: No
Other Closed Pull Requests
- SQLite Module Enhancements: This topic covers the introduction of a new 'location' method to the SQLite module in the Node.js project. The pull request includes several commits that add the method, handle unusual characters in tests, and incorporate review suggestions, culminating in its successful merge on April 21, 2025.
- Test Runner and Mocking Enhancements: This topic involves the addition of support for mocking JSON modules in the test runner of the Node.js project. The pull request includes the initial implementation, de-linting adjustments, and a test case to ensure import attributes remain necessary, along with a co-authored fix to avoid pre-loading the original module before testing rejection scenarios.
- Error Handling and Validation Improvements: This topic includes multiple pull requests focused on enhancing error handling and validation in the Node.js project. These changes involve stricter validation for the readline module, general error handling improvements by removing
ToLocalChecked()calls, and ensuring invalid lines inutil.parseEnv()are properly skipped.
- Documentation and Code Consistency Updates: This topic addresses updates to documentation and code consistency in the Node.js project. Pull requests include correcting the
AsyncLocalStorageexample, renaming test files to reflect updated function names, and correcting commit titles to comply with guidelines.
- Security and Testing Enhancements: This topic covers improvements in security and testing within the Node.js project. Pull requests include allowing penetration testing on live systems with prior authorization and introducing tests for signal handlers to investigate specific behaviors.
- Compilation and Code Optimization Fixes: This topic involves addressing compilation errors and optimizing code in the Node.js project. Pull requests include fixing a compilation error in
node_sea.ccand optimizing object prototype setting by eliminating unnecessary calls.
- Thread Safety and Concurrency Improvements: This topic addresses thread safety and concurrency issues in the Node.js project. Pull requests include implementing locking mechanisms in the
TaskQueueto prevent crashes and introducing support for raw header arrays in HTTP/2 methods.
- Miscellaneous Enhancements and Fixes: This topic includes various enhancements and fixes across the Node.js project. Pull requests cover a range of changes, from enhancing message clarity in
node --watchto addressing flakiness in specific tests and proposing changes to theImmediateobject.
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 |
|---|---|---|---|---|
| jasnell | 38 | 6 | 2 | 59 |
| aduh95 | 50 | 4 | 0 | 42 |
| dario-piotrowicz | 36 | 10 | 2 | 10 |
| anonrig | 16 | 7 | 0 | 31 |
| LiviaMedeiros | 25 | 3 | 3 | 18 |
| targos | 41 | 2 | 0 | 4 |
| marco-ippolito | 23 | 2 | 1 | 15 |
| geeksilva97 | 12 | 4 | 3 | 20 |
| mcollina | 25 | 2 | 1 | 10 |
| mertcanaltin | 21 | 2 | 0 | 14 |