I am not sure if this is specific to one extension or a more systemic thing, but there is at least one (malloydata.malloy-vscode, which can also come up if you just search "m") which has null files in the response and VS Code throws an error like can't access property "filter", i.files is null.

When I check the same version on Microsoft's marketplace, it does return files. It looks like the first version with null files is 0.3.1740680842.

This is the query VS Code is making:

{"filters":[{"criteria":[{"filterType":4,"value":"302cd8bd-1f55-4a51-8fc9-1382e357ca1e"},{"filterType":8,"value":"Microsoft.VisualStudio.Code"},{"filterType":12,"value":"4096"}],"pageNumber":1,"pageSize":1,"sortBy":0,"sortOrder":0}],"assetTypes":[],"flags":439}

Example snippet from the response:

"version": "0.3.1740680842",
"lastUpdated": "2025-02-27T18:28:46.113656Z",
"assetUri": "https://open-vsx.org/vscode/asset/malloydata/malloy-vscode/0.3.1740680842",
"fallbackAssetUri": "https://open-vsx.org/vscode/asset/malloydata/malloy-vscode/0.3.1740680842",
"files": null,

Newer versions do not have the problem, so maybe it was already fixed, and the extension needs to be re-indexed or something like that (or deleted), but I think there is no mechanism for that on the author's end, right?