nodejs - Debian Package Tracker

general

source: nodejs (main)
version: 20.19.2+dfsg-1
maintainer: Debian Javascript Maintainers (archive) (DMD)
uploaders: Jonas Smedegaard [DMD] – Jérémy Lal [DMD]
arch: all amd64 arm64 armel armhf i386 mips64el powerpc ppc64 ppc64el s390x
std-ver: 4.7.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 10.24.0~dfsg-1~deb10u1
o-o-sec: 10.24.0~dfsg-1~deb10u4
oldstable: 12.22.12~dfsg-1~deb11u4
old-sec: 12.22.12~dfsg-1~deb11u7
stable: 18.19.0+dfsg-6~deb12u2
stable-sec: 18.19.0+dfsg-6~deb12u1
testing: 20.19.0+dfsg1-1
unstable: 20.19.2+dfsg-1
exp: 22.14.0+dfsg-1

versioned links

10.24.0~dfsg-1~deb10u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
10.24.0~dfsg-1~deb10u4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
12.22.12~dfsg-1~deb11u4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
12.22.12~dfsg-1~deb11u7: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
18.19.0+dfsg-6~deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
18.19.0+dfsg-6~deb12u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
20.19.0+dfsg1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
20.19.2+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
22.14.0+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libnode-dev (1 bugs: 0, 1, 0, 0)
libnode115
nodejs (15 bugs: 0, 14, 1, 0)
nodejs-doc

action needed

Debci reports failed tests high

unstable: pass (log)
The tests ran in 0:03:44
Last run: 2025-05-15T14:36:19.000Z
Previous status: unknown

testing: pass (log)
The tests ran in 0:04:31
Last run: 2025-05-17T13:10:39.000Z
Previous status: unknown

stable: fail (log)
The tests ran in 0:03:39
Last run: 2025-05-11T16:36:33.000Z
Previous status: unknown

Created: 2024-09-07 Last update: 2025-05-19 12:31

2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:

CVE-2025-23165: In Node.js, the `ReadFileUtf8` internal binding leaks memory due to a corrupted pointer in `uv_fs_s.file`: a UTF-16 path buffer is allocated but subsequently overwritten when the file descriptor is set. This results in an unrecoverable memory leak on every call. Repeated use can cause unbounded memory growth, leading to a denial of service. Impact: * This vulnerability affects APIs relying on `ReadFileUtf8` on Node.js release lines: v20 and v22.
CVE-2025-23166: The C++ method SignTraits::DeriveBits() may incorrectly call ThrowException() based on user-supplied inputs when executing in a background thread, crashing the Node.js process. Such cryptographic operations are commonly applied to untrusted inputs. Thus, this mechanism potentially allows an adversary to remotely crash a Node.js runtime.

Created: 2025-05-15 Last update: 2025-05-19 08:00

12 security issues in bookworm high

There are 12 open security issues in bookworm.

12 important issues:

CVE-2023-46809: Node.js versions which bundle an unpatched version of OpenSSL or run against a dynamically linked version of OpenSSL which are unpatched are vulnerable to the Marvin Attack - https://people.redhat.com/~hkario/marvin/, if PCKS #1 v1.5 padding is allowed when performing RSA descryption using a private key.
CVE-2024-21892: On Linux, Node.js ignores certain environment variables if those may have been set by an unprivileged user while the process is running with elevated privileges with the only exception of CAP_NET_BIND_SERVICE. Due to a bug in the implementation of this exception, Node.js incorrectly applies this exception even when certain other capabilities have been set. This allows unprivileged users to inject code that inherits the process's elevated privileges.
CVE-2024-22019: A vulnerability in Node.js HTTP servers allows an attacker to send a specially crafted HTTP request with chunked encoding, leading to resource exhaustion and denial of service (DoS). The server reads an unbounded number of bytes from a single connection, exploiting the lack of limitations on chunk extension bytes. The issue can cause CPU and network bandwidth exhaustion, bypassing standard safeguards like timeouts and body size limits.
CVE-2024-22020: A security flaw in Node.js allows a bypass of network import restrictions. By embedding non-network imports in data URLs, an attacker can execute arbitrary code, compromising system security. Verified on various platforms, the vulnerability is mitigated by forbidding data URLs in network imports. Exploiting this flaw can violate network import security, posing a risk to developers and servers.
CVE-2024-22025: A vulnerability in Node.js has been identified, allowing for a Denial of Service (DoS) attack through resource exhaustion when using the fetch() function to retrieve content from an untrusted URL. The vulnerability stems from the fact that the fetch() function in Node.js always decodes Brotli, making it possible for an attacker to cause resource exhaustion when fetching content from an untrusted URL. An attacker controlling the URL passed into fetch() can exploit this vulnerability to exhaust memory, potentially leading to process termination, depending on the system configuration.
CVE-2024-27982: The team has identified a critical vulnerability in the http server of the most recent version of Node, where malformed headers can lead to HTTP request smuggling. Specifically, if a space is placed before a content-length header, it is not interpreted correctly, enabling attackers to smuggle in a second request within the body of the first.
CVE-2024-27983: An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.
CVE-2025-23083: With the aid of the diagnostics_channel utility, an event can be hooked into whenever a worker thread is created. This is not limited only to workers but also exposes internal workers, where an instance of them can be fetched, and its constructor can be grabbed and reinstated for malicious usage. This vulnerability affects Permission Model users (--permission) on Node.js v20, v22, and v23.
CVE-2025-23085: A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions. This vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x.
CVE-2025-23165: In Node.js, the `ReadFileUtf8` internal binding leaks memory due to a corrupted pointer in `uv_fs_s.file`: a UTF-16 path buffer is allocated but subsequently overwritten when the file descriptor is set. This results in an unrecoverable memory leak on every call. Repeated use can cause unbounded memory growth, leading to a denial of service. Impact: * This vulnerability affects APIs relying on `ReadFileUtf8` on Node.js release lines: v20 and v22.
CVE-2025-23166: The C++ method SignTraits::DeriveBits() may incorrectly call ThrowException() based on user-supplied inputs when executing in a background thread, crashing the Node.js process. Such cryptographic operations are commonly applied to untrusted inputs. Thus, this mechanism potentially allows an adversary to remotely crash a Node.js runtime.
CVE-2025-47153: Certain build processes for libuv and Node.js for 32-bit systems, such as for the nodejs binary package through nodejs_20.19.0+dfsg-2_i386.deb for Debian GNU/Linux, have an inconsistent off_t size (e.g., building on i386 Debian always uses _FILE_OFFSET_BITS=64 for the libuv dynamic library, but uses the _FILE_OFFSET_BITS global system default of 32 for nodejs), leading to out-of-bounds access. NOTE: this is not a problem in the Node.js software itself. In particular, the Node.js website's download page does not offer prebuilt Node.js for Linux on i386.

Created: 2024-02-16 Last update: 2025-05-19 08:00

debian/patches: 1 patch with invalid metadata high

Among the 19 debian patches available in version 20.19.2+dfsg-1 of the package, we noticed the following issues:

1 patch with invalid metadata that ought to be fixed.

Created: 2023-02-26 Last update: 2025-05-18 21:00

5 security issues in buster high

There are 5 open security issues in buster.

2 important issues:

CVE-2024-27982: The team has identified a critical vulnerability in the http server of the most recent version of Node, where malformed headers can lead to HTTP request smuggling. Specifically, if a space is placed before a content-length header, it is not interpreted correctly, enabling attackers to smuggle in a second request within the body of the first.
CVE-2024-27983: An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.

3 ignored issues:

CVE-2021-44531: Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the --security-revert command-line option.
CVE-2021-44532: Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.Versions of Node.js with the fix for this escape SANs containing the problematic characters in order to prevent the injection. This behavior can be reverted through the --security-revert command-line option.
CVE-2021-44533: Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.Affected versions of Node.js that do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation of certificate subjects may be vulnerable.

Created: 2024-04-03 Last update: 2024-06-29 13:15

Fails to build during reproducibility testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2022-04-04 Last update: 2025-05-19 12:01

3 bugs tagged patch in the BTS normal

The BTS contains patches fixing 3 bugs, consider including or untagging them.

Created: 2025-01-06 Last update: 2025-05-19 11:31

lintian reports 2 warnings normal

Lintian reports 2 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2025-05-18 Last update: 2025-05-18 22:02

version in VCS is newer than in repository, is it time to upload? normal

vcswatch reports that this package seems to have a new changelog entry (version 22.14.0+dfsg-2, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:

commit 7c20f7cafb9b53371791dd1712e77b629ad26e6c
Author: Jérémy Lal <kapouer@melix.org>
Date:   Wed Mar 19 00:20:17 2025 +0100

    Update changelog

commit 490ca54e8d5208b7bb293c9af32cbbbc0f1f5367
Author: Jérémy Lal <kapouer@melix.org>
Date:   Wed Mar 19 00:20:09 2025 +0100

    Recommends node-amaro

commit eeddbb5b49dd0cd14f3d0e89b6ad94ce2fb3a027
Author: Jérémy Lal <kapouer@melix.org>
Date:   Wed Mar 19 00:11:37 2025 +0100

    patch to allow amaro as external builtin

commit e7c988f8c6a197490de95fc4f53f6c05a92a4a5f
Author: Jérémy Lal <kapouer@melix.org>
Date:   Tue Mar 18 13:18:42 2025 +0100

    Enable optional amaro

Created: 2025-03-19 Last update: 2025-05-18 13:04

Build log checks report 2 warnings low

Build log checks report 2 warnings

Created: 2024-11-21 Last update: 2024-11-21 07:30

testing migrations

This package will soon be part of the auto-nodejs transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
excuses:
- Migration status for nodejs (20.19.0+dfsg1-1 to 20.19.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ autopkgtest for babel-minify/0.5.2+dfsg+~cs5.2.9-9: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-addon-api/8.3.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-base64url/3.0.1-9: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-browser-pack/6.1.0+ds+~6.1.3-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-buble/0.20.0+~0.20.1-5: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-chokidar/3.6.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-clean-css/5.3.3+~5.6.3-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-corepack/0.24.0-4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-eslint-plugin-node/11.1.0~ds-6: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Test in progress, armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), s390x: Failed (not a regression)
- ∙ ∙ autopkgtest for node-express/4.21.2+~cs8.36.27-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
- ∙ ∙ autopkgtest for node-flagged-respawn/1.0.1-5: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-gulp/4.0.2+~cs54.26.36-8: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-gyp/11.1.0+~5.0.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-jake/10.8.5+~1.0.4-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-katex/0.16.10+~cs6.1.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-lezer/1.4.16+~cs14.25.46-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-luxon/3.6.1+~3.6.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-mqtt/4.3.7-5: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-ncp/2.0.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-postcss/8.4.49+~cs9.2.32-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-proxy-agents/0~2024040606-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
- ∙ ∙ autopkgtest for node-tap-parser/13.0.1+~cs4.1.3-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-to-regex-range/5.0.1-4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-ts-jest/29.1.1+~cs0.2.6-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-webpack/5.97.1+dfsg1+~cs11.18.27-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for node-zx/7.1.1+~cs6.7.23-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for nodejs/20.19.2+dfsg-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for npm/9.2.0~ds1-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ missing build on riscv64
- ∙ ∙ blocked by freeze: is a key package (Follow the freeze policy when applying for an unblock)
- ∙ ∙ arch:riscv64 not built yet, autopkgtest delayed there
- ∙ ∙ Too young, only 1 of 20 days old
- Additional info:
- ∙ ∙ Updating nodejs will fix bugs in testing: #1105832
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nodejs.html
- ∙ ∙ Waiting for reproducibility test results on arm64 - info ♻
- ∙ ∙ Waiting for reproducibility test results on armhf - info ♻
- ∙ ∙ Waiting for reproducibility test results on i386 - info ♻
- Not considered

news

[rss feed]

[2025-05-18] Accepted nodejs 20.19.2+dfsg-1 (source) into unstable (Jérémy Lal)
[2025-05-11] nodejs 20.19.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2025-05-01] Accepted nodejs 12.22.12~dfsg-1~deb11u7 (source) into oldstable-security (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
[2025-05-01] Accepted nodejs 20.19.0+dfsg1-1 (source) into unstable (Jérémy Lal)
[2025-04-09] nodejs 20.19.0+dfsg-2 MIGRATED to testing (Debian testing watch)
[2025-04-03] Accepted nodejs 20.19.0+dfsg-2 (source) into unstable (Jérémy Lal)
[2025-03-24] nodejs 20.19.0+dfsg-1 MIGRATED to testing (Debian testing watch)
[2025-03-15] Accepted nodejs 22.14.0+dfsg-1 (source) into experimental (Jérémy Lal)
[2025-03-14] Accepted nodejs 20.19.0+dfsg-1 (source) into unstable (Jérémy Lal)
[2025-02-24] Accepted nodejs 12.22.12~dfsg-1~deb11u6 (source) into oldstable-security (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
[2025-02-20] nodejs 20.18.3+dfsg-1 MIGRATED to testing (Debian testing watch)
[2025-02-11] nodejs 20.18.2+dfsg-4 MIGRATED to testing (Debian testing watch)
[2025-02-11] Accepted nodejs 20.18.3+dfsg-1 (source) into unstable (Jérémy Lal)
[2025-02-02] Accepted nodejs 20.18.2+dfsg-4 (source) into unstable (Jérémy Lal)
[2025-02-01] Accepted nodejs 20.18.2+dfsg-3 (source) into unstable (Jérémy Lal)
[2025-02-01] Accepted nodejs 20.18.2+dfsg-2 (source) into unstable (Jérémy Lal)
[2025-01-26] Accepted nodejs 20.18.2+dfsg-1 (source) into unstable (Jérémy Lal)
[2025-01-11] nodejs 20.18.1+dfsg-2 MIGRATED to testing (Debian testing watch)
[2025-01-01] Accepted nodejs 20.18.1+dfsg-2 (source) into unstable (Jérémy Lal)
[2024-12-12] Accepted nodejs 22.12.0+dfsg-3 (source amd64 all) into experimental (Debian FTP Masters) (signed by: Jérémy Lal)
[2024-12-12] Accepted nodejs 22.12.0+dfsg-2 (source amd64 all) into experimental (Debian FTP Masters) (signed by: Jérémy Lal)
[2024-12-11] Accepted nodejs 22.12.0+dfsg-1 (source) into experimental (Jérémy Lal)
[2024-12-02] nodejs 20.18.1+dfsg-1 MIGRATED to testing (Debian testing watch)
[2024-11-20] Accepted nodejs 20.18.1+dfsg-1 (source) into unstable (Jérémy Lal)
[2024-11-18] nodejs 20.18.0+dfsg-2 MIGRATED to testing (Debian testing watch)
[2024-11-08] Accepted nodejs 20.18.0+dfsg-2 (source) into unstable (Jérémy Lal)
[2024-11-08] Accepted nodejs 20.18.0+dfsg-1 (source) into unstable (Jérémy Lal)
[2024-09-14] Accepted nodejs 12.22.12~dfsg-1~deb11u5 (source) into oldstable-security (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
[2024-09-01] nodejs 20.17.0+dfsg-2 MIGRATED to testing (Debian testing watch)
[2024-08-29] Accepted nodejs 20.17.0+dfsg-2 (source) into unstable (Jérémy Lal)

bugs [bug history graph]

all: 25 26
RC: 1
I&N: 21 22
M&W: 1
F&P: 2
patch: 3

links

homepage
lintian (0, 2)
buildd: logs, exp, checks, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 20.18.1+dfsg-1ubuntu2
48 bugs (1 patch)
patches for 20.18.1+dfsg-1ubuntu2