咨询npm audit --parseable列名文档及源码获取渠道

Great question! I’ve run into this exact confusion before with npm’s --parseable flag for audit outputs—official docs do tend to skip over these more niche details. Let’s break this down:

Finding Column Names for npm audit --parseable #

Unfortunately, the official v6 docs for npm audit don’t explicitly document the column order or meanings for the --parseable output. Your approach of cross-referencing with the default JSON output is actually the best workaround here.

For that final Y/N column you’re curious about: that indicates whether the vulnerability can be automatically fixed by running npm audit fix. Y means the fix is available via automatic dependency updates, while N means you’ll need to manually address the issue (like updating a package manually, changing dependencies, or applying a patch).

If you want to confirm the exact column mapping definitively, the most reliable source is the npm source code itself (which we’ll cover next)—the parseable output is generated directly from the same data used for the JSON report, so you can trace how each field maps to a column.

Accessing npm Audit Source Code #

Absolutely, npm audit’s source code is publicly available! npm is an open-source project, and the audit-related logic lives primarily in the lib/audit directory of the main npm repository. Specifically:

• The code that handles generating parseable output is likely in files like lib/audit/report.js or lib/audit/format.js, where the CLI formats audit results into different output types (JSON, parseable, human-readable).
• You can also look at lib/audit/index.js to understand how audit request/response data is structured before it’s formatted into output.

Even though the official docs don’t link directly to the source, you can navigate the repository to find exactly what you’re looking for.

内容的提问来源于stack exchange，提问作者stk1234