Change:
}, { "component": { <ins> "type": "other", "other": { "name": "H.264/AVC Video Standard", "downloadUrl": "https://chromium.googlesource.com/chromium/third_party/ffmpeg", "version": "4.4.git" } }, "licenseDetail": [ "This product is licensed under the AVC patent portfolio license for the personal", "and non-commercial use of a consumer to (i) encode video in compliance with the AVC standard ("AVC VIDEO")", "and/or (ii) decode AVC video that was encoded by a consumer", "engaged in a personal and non-commercial activity and/or was obtained from a video provider", "licensed to provide AVC video. No license is granted or shall be implied for any other use.", "Additional information may be obtained from MPEG LA LLC. See http://www.MPEGLA.COM.", "", "For clarification purposes, this notice does not limit or inhibit the use of the product", "for normal business uses that are personal to that business which do not include", "(i) redistribution of the product to third parties, or", "(ii) creation of content with AVC Standard compliant technologies for distribution to third parties." ], "version": "H.264 (08/21)", "isOnlyProductionDependency": true, "license": "OTHER" }, { "component": { </ins> "type": "git", "git": { "name": "nodejs",

Discussion:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --Greetings, I need to know all the dependencies vscode does have, recursively until I hit the transitive closure. I also need to know the version/license of each one of these dependencies. By dependencies I mean any piece of software it does require to run, whether is something you install at the OS level with, a bundled component/library, a nodejs/yarn package, a vscode internal extension, etc. Essentially, I want to know all the dependencies regardless of the "layer" at which these dependencies get used. I suspect the following resources sort of overlap with my request: But not sure if any of them is recursive my nature, and whether the union of all of the them gives me what I want. Would be great if Microsoft can compile a separate file containing all that information. It will help with adoption of vscode within organizations. Thanks. PS: It would be great to have such list for both open-source vscode and the Microsoft build.
By the way, to avoid duplication of work, I would like to share that I have asked earlier same question on StackOverflow: But later on I realized that filing my request here would get more traction. On any case, I will be happy to provide more information if my request is not entirely clear. Thanks in advance
In the VS Code installation directory, you can find two files which list the licenses of the third party software that is distributed with VS Code: and . In the root of this repository, you can find a file called which contains the third party software that is incorporated in this repository.
Hi Alex, Thanks for you reply. Could you also clarify whether, for the case of VS Code, those two files are the transitive closure of the dependencies? Meaning that they cover all recursive dependencies. If they do not, please share up to what level they include. Another question I have is whether these 3 files: should be also considered. They seem to mention stuff that is not present on the files you mentioned. Saludos + regards.
In the VS Code installation directory, the two files and contain the licenses of all third party software distributed with VS Code.

Note that the file present in the VS Code installation directory is not equal to the from the root of this repository. Could you please give a specific example of what is missing?
Hello Alex, Thanks for clarifying that the included with VS Code, is a super-set of that included for the OSS repo. I will focus next questions on the VS Code one. Just to finish the point about these dependencies being recursive or not, please confirm the following: say VS Code requires component X, which in turn needs Y which in turn needs Z. So we have a chain of depth 3 for these dependencies: X -Y -Z. The three dependencies X, Y and Z will be mentioned either on or , is that the case? If it is, will this generalize to any depth of the dependency chain? And finally on the example of something missing at , let us take very first entry: { // Reason: The license at // does not include a clear Copyright statement and does not credit authors. "name": "jschardet", "prependLicenseText": [ "Chardet was originally ported from C++ by Mark Pilgrim. It is now maintained", " by Dan Blanchard and Ian Cordasco, and was formerly maintained by Erik Rose.", " JSChardet was ported from python to JavaScript by António Afonso ", " () and transformed into an npm package by ", "Markus Ast ()" ] }, jschardet does not seem mentioned on nor Same thing seem to happen for any other name mentioned on or Perhaps I am misinterpreting the content of those files, but they seem like dependencies to me and hence wondered if they should be considered as well if I want to gather the whole set. Thank you.
Hello Alex, Any further comments? I want to call it a day but those pending question prevent proper sleep :-} Thanks.
jschardet is in , but make sure you're looking at the one for the installed program, rather than the one in this repository. In the Windows system install, for example, the file is in the folder.
You are absolutely right, Alex. I was searching with an editor and that did not bring any result, but grepping did. Still, I can see these 5 dependencies in [] but not on Please also comment about the recursivity question. Thanks again.
Hi, this is Raymond.

I think the dependencies listed do form a transitive closure, considering how even shows up in the generated file for . As for the five dependencies, is in the generated file of the latest Insiders. The generated file you are seeing might be for the latest stable version, instead. I noticed that isn't in the generated , but it's also not used in the lockfile. In the best case, that means the notices file generator is trimming libraries that aren't being used in the product. But, is also not in the latest generated notices
Hi Raymond, Thank you for confirming that generated does contain the transitive closure of dependencies, indeed. As for the missing ones, it may be good to re-generate to ensure it does include any missing piece (if any). Cheers
I see that is missing from , thank you for raising that. We will correct this ASAP.
Great, thank you Alex, Raymond and everyone involved. Great support, super responsive.