You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 21, 2025. It is now read-only.
-Check either the runtime version of Node.js, or a supplied version
35
-
-Display end-of-life dates for a given version of Node.js
36
-
-Display new releases for a given version of Node.js with configurable specificity (latest/minor/patch)
37
-
-Patch: 16.13.0 -> 16.13.2
38
-
-Minor: 16.13.0 -> 16.14.2
39
-
-Latest: 16.13.0 -> 17.9.0
40
-
-Rules automatically updated daily. Information is sourced directly from nodejs.org - you'll never be waiting on someone like me to merge a pull request before getting the latest patch information.
41
-
-Multiple interfaces: CLI (via NPM), Docker, direct code import
42
-
-Easily scriptable for use with CI/CD workflows. All Docker/CLI outputs are in JSON format to be consumed with your favorite tools - such as [jq](https://stedolan.github.io/jq/)
43
-
-Configurable exit conditions. Use CLI flags like `--fail-security` to set a failure exit code if the given version of Node.js has a known CVE or is no longer supported.
44
-
-Zero dependencies
33
+
- List known CVEs for a given version of Node.js
34
+
- Check either the runtime version of Node.js, or a supplied version
35
+
- Display end-of-life dates for a given version of Node.js
36
+
- Display new releases for a given version of Node.js with configurable specificity (latest/minor/patch)
37
+
- Patch: 16.13.0 -> 16.13.2
38
+
- Minor: 16.13.0 -> 16.14.2
39
+
- Latest: 16.13.0 -> 17.9.0
40
+
- Rules automatically updated daily. Information is sourced directly from nodejs.org - you'll never be waiting on someone like me to merge a pull request before getting the latest patch information.
41
+
- Multiple interfaces: CLI (via NPM), Docker, direct code import
42
+
- Easily scriptable for use with CI/CD workflows. All Docker/CLI outputs are in JSON format to be consumed with your favorite tools - such as [jq](https://stedolan.github.io/jq/)
43
+
- Configurable exit conditions. Use CLI flags like `--fail-security` to set a failure exit code if the given version of Node.js has a known CVE or is no longer supported.
44
+
- Zero dependencies
45
45
46
46
## Example:
47
47
@@ -141,37 +141,37 @@ Get the latest Node.js 17 release version directly from the rules using [curl](h
141
141
142
142
### Output
143
143
144
-
-auditVersion: string - The version of Node.js that is being audited.
145
-
-hasVulnerabilities: bool - If the auditVersion has any known CVEs or not.
146
-
-hasSupport: bool - If the auditVersion is still receiving support.
147
-
-supportType: string - The current support status of auditVersion: 'current'|'active'|'maintenance'|'none'.
148
-
-isLatestPatchVersion: bool - If auditVersion is the latest patch-level release (17.9.x).
149
-
-isLatestMinorVersion: bool - If auditVersion is the latest minor-level release (17.x.x).
150
-
-isLatestVersion: bool - If auditVersion is the latest release (x.x.x).
151
-
-latestPatchVersion: string - The latest patch-level version for auditVersion.
152
-
-latestMinorVersion: string - The latest minor-level version for auditVersion.
153
-
-latestVersion: string - The latest Node.js version.
154
-
-activeSupportEndDate: string|null - ISO8601 formatted date for the end of active support for auditVersion.
155
-
-supportEndDate: string|null - ISO8601 formatted date for the end of maintenance support for auditVersion.
156
-
-rulesLastUpdatedDate: string - ISO8601 formatted date for the last time the rules were auto-updated.
157
-
-vulnerabilities: object - CVEs known to affect auditVersion with details about the CVE. CVE Details might be null for recently discovered CVEs.
144
+
- auditVersion: string - The version of Node.js that is being audited.
145
+
- hasVulnerabilities: bool - If the auditVersion has any known CVEs or not.
146
+
- hasSupport: bool - If the auditVersion is still receiving support.
147
+
- supportType: string - The current support status of auditVersion: 'current'|'active'|'maintenance'|'none'.
148
+
- isLatestPatchVersion: bool - If auditVersion is the latest patch-level release (17.9.x).
149
+
- isLatestMinorVersion: bool - If auditVersion is the latest minor-level release (17.x.x).
150
+
- isLatestVersion: bool - If auditVersion is the latest release (x.x.x).
151
+
- latestPatchVersion: string - The latest patch-level version for auditVersion.
152
+
- latestMinorVersion: string - The latest minor-level version for auditVersion.
153
+
- latestVersion: string - The latest Node.js version.
154
+
- activeSupportEndDate: string|null - ISO8601 formatted date for the end of active support for auditVersion.
155
+
- supportEndDate: string|null - ISO8601 formatted date for the end of maintenance support for auditVersion.
156
+
- rulesLastUpdatedDate: string - ISO8601 formatted date for the last time the rules were auto-updated.
157
+
- vulnerabilities: object - CVEs known to affect auditVersion with details about the CVE. CVE Details might be null for recently discovered CVEs.
158
158
159
159
## Project Goals:
160
160
161
-
-Always use update-to-date information and fail if it becomes too stale. Since this tool is designed to help its users stay informed, it must in turn fail if it becomes outdated.
162
-
-Fail if the requested information is unavailable. ex. auditing an unknown version of Node.js like 12.50.0, or 0.9.0. Again, since this tool is designed to help its users stay informed, it must in turn fail if the requested information is unavailable.
163
-
-Work in both open and closed networks (as long as the tool is up-to-date).
164
-
-Minimal footprint and dependencies (no runtime dependencies).
165
-
-Runtime support for the oldest supported version of Node.js. If you are using this tool with an unsupported version of Node.js, then you already have all the answers that this tool can give you: Yes, you have vulnerabilities and are out of date. Of course that is just for the run-time, it is still the goal of this project to supply information about any reasonable version of Node.js.
161
+
- Always use update-to-date information and fail if it becomes too stale. Since this tool is designed to help its users stay informed, it must in turn fail if it becomes outdated.
162
+
- Fail if the requested information is unavailable. ex. auditing an unknown version of Node.js like 12.50.0, or 0.9.0. Again, since this tool is designed to help its users stay informed, it must in turn fail if the requested information is unavailable.
163
+
- Work in both open and closed networks (as long as the tool is up-to-date).
164
+
- Minimal footprint and dependencies (no runtime dependencies).
165
+
- Runtime support for the oldest supported version of Node.js. If you are using this tool with an unsupported version of Node.js, then you already have all the answers that this tool can give you: Yes, you have vulnerabilities and are out of date. Of course that is just for the run-time, it is still the goal of this project to supply information about any reasonable version of Node.js.
166
166
167
167
## Acknowledgments & License
168
168
169
-
-This project is released under the [Apache License 2.0](https://raw.githubusercontent.com/lightswitch05/node-version-audit/master/LICENSE).
170
-
-The accuracy of the information provided by this project cannot be verified or guaranteed. All functions are provided as convenience only and should not be relied on for accuracy or punctuality.
171
-
-The logo was created using Mathias Pettersson and Brian Hammond's [Node.js Logo](https://nodejs.org/en/about/resources/#logo-downloads) as the base image. The logo has been modified from its original form to include overlay graphics.
172
-
-This project and the use of the modified Node.js logo is not endorsed by Mathias Pettersson or Brian Hammond.
173
-
-This project and the use of the Node.js name is not endorsed by OpenJS Foundation.
174
-
-CVE details and descriptions are downloaded from National Institute of Standard and Technology's [National Vulnerability Database](https://nvd.nist.gov/). This project and the use of CVE information is not endorsed by NIST or the NVD. CVE details are provided as convenience only. The accuracy of the information cannot be verified.
175
-
-Node.js release details and support dates are generated from [Changelogs](https://github.com/nodejs/node/tree/master/doc/changelogs) and the [Release Schedule](https://github.com/nodejs/Release/blob/main/schedule.json). The accuracy of the information cannot be verified.
169
+
- This project is released under the [Apache License 2.0](https://raw.githubusercontent.com/lightswitch05/node-version-audit/master/LICENSE).
170
+
- The accuracy of the information provided by this project cannot be verified or guaranteed. All functions are provided as convenience only and should not be relied on for accuracy or punctuality.
171
+
- The logo was created using Mathias Pettersson and Brian Hammond's [Node.js Logo](https://nodejs.org/en/about/resources/#logo-downloads) as the base image. The logo has been modified from its original form to include overlay graphics.
172
+
- This project and the use of the modified Node.js logo is not endorsed by Mathias Pettersson or Brian Hammond.
173
+
- This project and the use of the Node.js name is not endorsed by OpenJS Foundation.
174
+
- CVE details and descriptions are downloaded from National Institute of Standard and Technology's [National Vulnerability Database](https://nvd.nist.gov/). This project and the use of CVE information is not endorsed by NIST or the NVD. CVE details are provided as convenience only. The accuracy of the information cannot be verified.
175
+
- Node.js release details and support dates are generated from [Changelogs](https://github.com/nodejs/node/tree/master/doc/changelogs) and the [Release Schedule](https://github.com/nodejs/Release/blob/main/schedule.json). The accuracy of the information cannot be verified.
0 commit comments