Weekly GitHub Report for Node: April 07, 2025 - April 14, 2025 (14:18:43)
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.
-
Optional deprecation phase between
RuntimeandEnd-of-Life: This issue discusses the proposal to introduce an additional "throwing deprecation" phase between the current runtime deprecation warning phase and the complete removal of a deprecated feature at its End-of-Life. The goal of this new phase is to compel users to update their code or limit the maximum supported Node.js version, thereby preventing unexpected behavior in user code that relies on deprecated features after the End-of-Life phase.- The comments debate the necessity of a new deprecation phase, with some suggesting that a thrown error at the End-of-Life stage could suffice. Concerns are raised about runtime deprecations being ignored, and the idea of introducing a throwing phase to delay End-of-Life is discussed. The conversation also touches on whether there have been precedents for removing throws in subsequent major releases.
- Number of comments this week: 3
-
Unable to build node 23.11 with llvm15, clang 15 and libc++ 15: This issue involves a user encountering errors while attempting to build Node version 23.11 using LLVM 15, Clang 15, and libc++ 15, specifically related to missing templates and members in the standard library. The user notes that the last successful build with these tools was version 23.6.1 and seeks advice on resolving the persistent errors despite trying to append experimental flags to Clang.
- The comments suggest that a specific commit may have introduced the issue, and it is noted that Node is not tested with Clang 15, with a recommendation to use Clang 16.0 for compatibility. There is also a suggestion to adjust the warning threshold for Clang in the project's configuration file.
- Number of comments this week: 3
-
REPL doesn't work with nested proxies: This issue describes a bug in the Node.js REPL where attempting to access nested properties on a proxy object triggers the proxy prematurely, preventing the expected behavior of accessing properties like
obj.hello.world. The problem consistently occurs and is believed to be related to the REPL's input preview or completer functionality, which inspects the input and inadvertently triggers the proxy.- The comments discuss the issue being related to the REPL's input preview and completer, with examples provided to reproduce the problem. A suggestion is made to disable the completer for nested object fields as a potential solution, possibly behind a flag, acknowledging it as a known limitation.
- Number of comments this week: 3
-
cannot read stored value in asynclocalstorage when using finished: This issue involves a bug in Node.js where the
AsyncLocalStorageis unable to read a stored value when using thefinishedfunction from thestreammodule, resulting in anundefinedvalue instead of the expected stored value. The problem consistently occurs on Linux platforms with Node.js version v22.14.0 and possibly earlier versions, and it affects the use of thefinishedfunction within thebody-parserpackage, which is part of an effort to transition away from usingon-finished.- The comments suggest using ES module syntax instead of
requirefor modern compatibility, propose usingstream.promises.finishedfor better error handling with async/await, and confirm that thefinishedfunction is not capturing the async context correctly. - Number of comments this week: 3
- The comments suggest using ES module syntax instead of
-
v22.x-staging cherry-pick status: This issue is about the cherry-pick status for the
v22.x-stagingbranch in the Node.js project, detailing the successful and failed cherry-picks of various commits. The report highlights several issues, including the lack of automatic report creation on GitHub, the need for manual label placement, and suggestions for improving the cherry-pick process.- The comments discuss the challenges faced during the cherry-pick process, such as the absence of a two-week baking period for LTS, the need for manual report creation and label placement, and the suggestion to streamline the process by automating certain steps. The feedback will be incorporated into the original pull request for further improvements.
- 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.
- Flaky GC-related tests with V8 12.2: This issue addresses the problem of flaky garbage collection-related tests in the V8 12.2 environment, specifically concerning the
test-shadow-realm-gc-module,test-shadow-realm-gc, andtest-net-write-fully-async-hex-string. The proposed temporary solution is to skip these tests due to their unreliability, as they may be failing because of incorrect assumptions about V8's new garbage collection strategy rather than actual bugs, with a suggestion to track the issue for future resolution. - 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 open for over a year. The test intermittently fails due to a timeout, suggesting potential underlying bugs or broken timing assumptions, and it has been suggested to mark it 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 same code functions correctly in version v21.6.2 and earlier. - sequential/test-fs-watch and a few fs/watch related tests being flaky: This issue highlights a problem with the
sequential/test-fs-watchand other related file system watch tests being flaky on the AIX platform, where they frequently fail due to reaching the system limit for the number of file watchers. The error, identified by theENOSPCcode, indicates that the system cannot allocate additional file watchers, causing the tests to fail with an exit code of 1, and this pattern of failure has been observed across multiple related tests.
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: 13
Summarized Issues:
- Flaky Tests: The issue with the flaky test
test-fs-stat-biginton the SmartOS platform involves an assertion error due to a mismatch between expected and actual BigInt values, causing the test to fail. This highlights the challenges in ensuring test reliability across different platforms and the need for consistent test environments.
- Cherry-Pick Process: The cherry-pick status report for the
v22.x-stagingbranch of Node.js reveals 100 successful cherry-picks, 65 failures, and 3 ignored commits. The process faces challenges such as the lack of automatic report creation and the need for manual label placement, suggesting improvements for efficiency.
- Deprecation Strategy: A proposal to introduce a "throwing deprecation" phase aims to compel users to update their code before the complete removal of a deprecated feature. This strategy seeks to balance user compliance with the goal of feature removal in the next major release.
- HTTP/2 Subsystem Bug: A bug in the HTTP/2 subsystem prevents clients from receiving the expected GOAWAY frame and response header when a server closes a session after responding with an empty body. This issue consistently reproduces under specific conditions, indicating a need for a robust fix.
- SQL Query Execution: Challenges in executing multi-statement SQL queries using
node:sqlitefor an educational platform include the inability ofexec()to return results and the need for intelligent statement splitting. Existing parsing libraries have limitations, necessitating a more effective solution.
- Build Failures with LLVM: Building Node version 23.11 with LLVM 15, Clang 15, and libc++ 15 fails due to missing template and member names in the
std::rangesnamespace. Attempts to resolve the issue by appending-fexperimental-libraryto Clang were unsuccessful, with the last successful build being version 23.6.1.
- Date Representation Change: In Node.js version 20.15.0, the
utils.format()function with the%sspecifier outputs a different date representation than previous versions. This deviation from expected behavior is suspected to be introduced by a specific pull request.
- REPL Proxy Behavior: The Node.js REPL prematurely triggers a proxy's getter when accessing nested properties due to input preview or completer. This behavior is unexpected and affects the usability of proxy objects in the REPL environment.
- Snapshot File Format Customization: A feature request to allow customization of snapshot file formats in a test runner aims to enable users to define a custom parser for more human-readable formats. This would improve readability and highlight capabilities over the default format.
- Build System Python Path: The Node build system incorrectly prioritizes a hardcoded path to /usr/bin/python3.13 over the /usr/bin/python symlink, causing build errors. It is suggested that the build system should first check and honor the symlink to ensure compatibility.
- DNS Resolver Timeout: In Node.js versions v20.17.0 or greater, the DNS Resolver's timeout configuration is not honored due to changes in the c-ares library. This results in premature timeouts when DNS servers are slow, as the library calculates its own timeout based on network conditions.
- AsyncLocalStorage Bug: The
finishedfunction from thestreammodule fails to access a value stored inAsyncLocalStorageduring an HTTP request, returningundefinedinstead of the expected value. This affects thebody-parserpackage and is part of a transition to native Node.js APIs.
- WSL Terminal Behavior: Running a Node.js script in the background on a WSL Ubuntu environment changes the terminal's stty settings from
echoto-echo, causing display issues. Althoughstty echocan fix it, the user questions whether this behavior is a bug.
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:
- Error Message Formatting in Node.js: The issue with error message formatting in Node.js arises when a cyclic dependency is created between CommonJS and ES modules. The confusion is primarily due to the term 'madated' and the overall clarity of the message, which can mislead developers.
- Node.js HTTP/2
writeHeadFunctionality: Node.js is considering transitioning from warnings to errors when using thewriteHeadfunction with astatusMessagein HTTP/2. This change, proposed for future versions 25 or 26, would be a breaking change but aims to improve protocol compliance.
- Node.js DatabaseSync Timeout Proposal: A proposal to add a "timeout" option for DatabaseSync in node:sqlite aims to prevent "database is locked" errors. By allowing users to set a busy_timeout value greater than the default of 0, this change seeks to enhance database operation reliability.
- Node.js
--test-timeoutFlag Bug: A bug in the--test-timeoutflag causes the timeout to apply to the entire module rather than individual tests. This results in test failures if the cumulative execution time exceeds the specified timeout, contrary to the expected behavior.
- Node.js Version Specification Proposal: A proposal to add a "version" field to the
node.config.jsonfile aims to specify the Node.js version required for running an application. This change seeks to prevent version mismatches and enhance security scanning, while considering existing alternatives.
- Node.js Timezone Bug: A bug in the Node.js environment incorrectly sets the America/Asuncion timezone to UTC-4 instead of UTC-3. This issue, attributed to outdated ICU timezone data, has been resolved in a newer Node.js version with updated ICU data.
- Node.js Memory Leak in
ReadFileUtf8: A memory leak occurs in thenode::fs::ReadFileUtf8function when the first argument is a string. This issue causes the resident set size (rss) memory usage to increase indefinitely due to missing cleanup calls after file operations.
- Node.js Build Failure with LLVM 15: Building Node version 23.11 using LLVM 15, Clang 15, and libc++ 15 fails due to missing template and member definitions in the
std::rangesnamespace. Attempts to resolve the issue by appending-fexperimental-libraryto Clang have been unsuccessful.
- Miscellaneous GitHub Issues: Several issues pertain to specific job failures, minimal descriptions, or lack of details in GitHub projects. These include a GitHub Actions workflow failure, a concern related to a 'Bot', and closed issues with minimal information.
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: 30
Key Open Pull Requests
1. 2025-04-15, Version 22.15.0 'Jod' (LTS), @RafaelGSS: This pull request introduces the 22.15.0 'Jod' (LTS) version of Node.js, featuring several notable changes including the implementation of partial error comparison and performance improvements in the assert module, support for --use-system-ca on Windows and macOS in the crypto module, the addition of TLSA record query and parsing in the dns module, and the introduction of new methods and hooks in the module, process, and sqlite modules, among other enhancements and updates.
- URL: pull/57840
- Merged: No
- 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. esm: implement import.meta.main: This pull request implements the import.meta.main feature in the Node.js project, which introduces a boolean value to determine if an ES Module is the entry point of the current process, thereby addressing issue #57226 and superseding a previous pull request #32223, while also including various fixes, improvements, and style adjustments to ensure accurate functionality and documentation.
- URL: pull/57804
- Merged: No
3. http2: fix graceful session close: This pull request addresses an issue in the Node.js HTTP/2 implementation where the session.close() method prematurely terminated sessions when response.end() was invoked with an empty payload while active streams were still present, ensuring that sessions now close gracefully only after all streams have completed and clients have received the GOAWAY frame, in compliance with the HTTP/2 specification.
- URL: pull/57808
- Merged: No
Other Open Pull Requests
- Formatting Objects with Symbol.toPrimitive: This topic involves enhancing the
inspectfunction to work with objects having a built-inSymbol.toPrimitive, similar totoString. The pull request includes multiple commits for fixing the issue, adding tests, and handling cases wheretoPrimitiveis defined in the prototype.
- CodeQL Analysis Tool Addition: The addition of a nightly CodeQL analysis tool to the Node.js project is proposed, with multiple fixup commits refining the implementation. This effort is overseen by the Node.js Security Working Group to enhance security practices.
- OpenSSL and Cryptographic Functions Update: This topic covers updating the OpenSSL dependency to version 3.5 and migrating cryptographic functions to use OpenSSL's EVP_KDF functions. The updates involve switching the OpenSSL updater, upgrading sources, and addressing issues like parameter handling and error reporting.
- Corepack and Documentation Updates: The future removal of Corepack in Node.js version 25 is clarified, with documentation updates highlighting this change. The updates include a call to action for existing users, similar to the approach for the punycode module.
- Test Runner and Coverage Improvements: Modifications to the test runner and coverage report are proposed to recalculate run duration and ensure accurate coverage display. These changes address issues with unchanged duration across reruns and omitted files with short names.
- Node.js Crypto Module Enhancements: Enhancements in the crypto module include addressing unsafe usage of
std::string_viewand renaming a misleading argument in thecreateCipherBasefunction. These changes ensure proper handling of C-style strings and align argument names with their semantics.
- Node.js Web Crypto API Fixes: An issue in the Web Crypto API is addressed by modifying the
isNonSharedArrayBuffer()function to validate ArrayBuffer instances across different JavaScript realms. This ensures compatibility and performance across contexts.
- Node.js Embedding and API Enhancements: Enhancements include converting the
v8impl::NewEnvfunction tonode_napi_env__::Newand introducing a new C FFI compatible function,node_start(). These changes facilitate Node.js embedding and API usage in C FFI environments.
- Release and Workflow Improvements: Improvements to the release-lint tool and "create-release-proposal" workflow are proposed to support semver-major releases and handle long pull request bodies. These changes ensure proper functionality and performance in release processes.
- Miscellaneous Node.js Enhancements: Various enhancements include updating the
util.parseEnv()function, reducing code duplication in the zlib module, and addressing documentation z-index issues. These changes improve functionality, code quality, and user experience.
- SQLite and OpenSSL Component Management: The SQLite online backup API is backported to the v22.x branch, and OpenSSL demos, documentation, and test folders are proposed for removal. These changes ensure functionality and streamline component management.
- Signal Handlers and Test Investigations: Tests for signal handlers are introduced to investigate problematic behavior affecting other tests. This effort aims to reproduce issues without merging into the main codebase.
- Zstd Update Tool Proposal: A tool to update
zstdwithin the Node.js workflow is proposed, as indicated by the title and commit messages. This proposal is currently not merged.
- Fast API Calls for util.types: The implementation of fast API calls for
util.typesis proposed to enhance performance across various APIs. Local benchmarks indicate significant improvements in execution speed for certain data types and methods.
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: 41
Key Closed Pull Requests
1. Elp: This pull request involves the creation and integration of several YAML configuration files, such as npm-publish-github-packages.yml, google.yml, npm.yml, and codeql.yml, into the Node.js project, although it was ultimately not merged.
- URL: pull/57812
- Merged: No
- Associated Commits: d21fc, 62c68, 467f2, d0b9e, 64abc, 3e121, bac58, 9b920, c6972, 1ed76, b0cca, 8536f, 0a2d9, 9c861
2. doc: graduate more experimental APIs: This pull request involves updating the documentation to graduate several experimental APIs, including events.addAbortListener, multiple process APIs, and util.aborted, to stable status within the Node.js project.
- URL: pull/57765
- Merged: No
3. test: add tests for REPL custom evals: This pull request adds tests for custom REPL evaluations in the Node.js project, addressing a previously noted TODO comment, and includes multiple commits such as adding the tests, applying code review suggestions, reorganizing the getReplOutput function, and adjusting tests to use concurrency.
- URL: pull/57691
- Merged: 2025-04-07T22:09:34Z
Other Closed Pull Requests
- Corepack Removal Documentation: The documentation for Node.js has been updated to clarify the removal of Corepack in version 25 and beyond. This includes ensuring the existing documentation remains accessible due to widespread backlinks, with plans for its eventual removal by April 2028.
- Test Runner Timeout Bug: A bug in the test runner was fixed by changing the
--test-timeoutsetting to apply per test, ensuring consistent timeout behavior. Additionally, the issue where the--test-timeoutwas not respected when running tests without the--testflag was resolved.
- REPL Documentation Clarifications: The REPL documentation was improved by clarifying the examples section and correcting the alert about production use. This ensures the examples are distinct from the section on running multiple REPL instances and prevents misinterpretation.
- Node.js Script and Flag Removals: The
nocorepackflag was removed from thevcbuildscript, and the unusedosx-pkg-postinstall.shscript was deleted. These removals were made because they were either overlooked in previous updates or replaced by other scripts.
- Error Handling Enhancements: Several pull requests aimed to enhance error handling across various Node.js modules, including
crypto_x509,callback.cc,node_messaging,node_http2, andnode_env_var.cc. These changes were proposed to improve robustness, although not all were merged.
- Memory Management and Performance Improvements: Improvements were made to memory management in the file system module and performance enhancements in the
globSyncfunction. These changes aim to prevent memory leaks and improve performance across different scenarios.
- Typographical and Formatting Corrections: Minor corrections were made to improve the formatting of error messages and correct typographical errors. These changes enhance clarity and resolve specific issues like #57451.
- Test Flakiness and Temporary File Removal: Efforts were made to reduce test flakiness by distributing tests into multiple files, and temporary files were removed from the merging process. These changes aim to enhance test reliability and streamline the development process.
- Security and Alignment Fixes: A critical typo in the HTTP/2 implementation was corrected to address a security vulnerability, and pointer alignment issues in the zlib module were fixed. These changes prevent potential security risks and bus errors.
- AsyncLocalStorage Enhancements: The
AsyncLocalStoragewas enhanced by addingdefaultValueandnameoptions. These changes align it more closely with the upcomingAsyncContextspecification.
- DatabaseSync Timeout Options: Timeout options were added to the DatabaseSync functionality in the SQLite module. This change moves the timeout configuration to the open configuration phase, enhancing the module's flexibility.
- SafeMap Primordial Usage: The use of a SafeMap primordial for the
ActiveAsyncContextFramewas corrected. This change ensures proper extension and utilization of primordials in the Node.js project.
- Flatpak URL Scheme Addition: A new URL scheme, "flatpak+https," was proposed for Linux systems to display Flatpak packages. This addition addresses issues with routers not recognizing the scheme as a valid
slashedProtocol.
- Deprecated Function Wrapping: A solution was proposed to preserve the
lengthproperty in deprecated functions by wrapping them in aProxy. This approach also mitigates prototype pollution.
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 | 56 | 8 | 0 | 69 |
| aduh95 | 71 | 10 | 0 | 48 |
| targos | 64 | 3 | 0 | 14 |
| dario-piotrowicz | 47 | 13 | 2 | 14 |
| mertcanaltin | 41 | 4 | 0 | 13 |
| cjihrig | 14 | 0 | 1 | 35 |
| anonrig | 13 | 0 | 0 | 32 |
| marco-ippolito | 16 | 1 | 2 | 18 |
| ljharb | 2 | 1 | 0 | 32 |
| AugustinMauroy | 22 | 1 | 1 | 10 |