velociraptor-docs icon indicating copy to clipboard operation
velociraptor-docs copied to clipboard

Add artifact listing VS Code extensions

Open misje opened this issue 10 months ago • 3 comments

This is a rather simple artifact, but it is still useful. The information gathered would be more useful if tied together with extension information fetched from the unofficial marketplace API. I have a nearly finished notebook suggestion that does just that, but due to the sheer number of extensions (+72k) and API rate limits, I am not sure if it is stable or useful. Example:

2025-04-04_19-16

misje avatar Apr 04 '25 17:04 misje

Here is an example of the complete list of extensions fetched from the unofficial marketplace API, which probably has many use cases. Even if its metadata is not used at all, it could be used to cross-reference extensions that has been removed/revoked from the marketplace(?):

2025-04-04_19-24

misje avatar Apr 04 '25 17:04 misje

If we are restricted by API limitations we can mirror the API in a JSON file and host it statically on github. This would make it a useful resource and allow everyone to use it easily

scudette avatar Apr 05 '25 02:04 scudette

If we are restricted by API limitations we can mirror the API in a JSON file and host it statically on github. This would make it a useful resource and allow everyone to use it easily

That is also an alternative. I will look into that in the next pull request adding this feature.

Would it be better to just upload the files rather than include them in the JSON blob? We try to avoid that as it can explode the size of the JSON responses and lead to issues in the GUI.

Personally I do not think so. The files are typically very small. In my recent hunt, the results show that most have a few extensions installed, some about 20. The most extreme case is 78. Each extension entry is not large. Does this warrant file uploads instead? I have yet to experience GUI issues due to large JSON data in any of the artifacts I have ever used, but I would like to know more about when it becomes an issue, and adapt artifacts if needed.

misje avatar Apr 05 '25 08:04 misje

Yes it is always necessary to upload the files - then you get the preview box for free and can export them easily as files.

Including bulk data inside JSON is almost always a bad idea

scudette avatar Apr 11 '25 07:04 scudette