Provide details for when your extension has suspicious content

[estruyf]

I wanted to publish a new version of my extension, and I got the following message:

Your extension has suspicious content. Please fix your extension metadata, or reach contact support if you need assistance.

There hasn't been a change to the extension metadata since the last release. Not sure why it is happening. Also, it would be great to point out the actual issue.

[estruyf]

Just verified the documentation again and did a couple of tests, the same happens on the Manage Publishers & Extensions page.

At least, there is a pointer to the docs which point out that the following constraints are checked:

• The icon provided in package.json may not be an SVG.
• The badges provided in the package.json may not be SVGs unless they are from trusted badge providers.
• Image URLs in README.md and CHANGELOG.md need to resolve to https URLs.
• Images in README.md and CHANGELOG.md may not be SVGs unless they are from trusted badge providers.

I validated this myself, and all should be valid. Just to make sure I did the following:

• Cleared out the readme and only kept the title in it.
• Verified that no images are used in the changelog
• Removed badges

Packaged and uploaded the vsix file again, but still, validation fails.

[prashantvc]

@estruyf I apologies you have to experience this. Could you share your extension details? We will take a look

[estruyf]

Here is my compressed vsix file. Hope this helps.

vscode-front-matter-beta-7.0.1956421.vsix.zip

[prashantvc]

Appreciate your patience while we investigate the issue. I will see if we can provide you a workaround in the meantime

[tronical]

We're running into the same error message when trying to update our extension. Do you know what could cause this error message?

[gareth-rees]

I encountered the same problem trying to update the Time Travel Debug for C/C++ extension. Here's a screenshot of the error message:

I was unable to contact marketplace support due to issue #347. I've attached the offending .vsix in case that will help diagnose the problem: udb-1.2.0.vsix.zip

[prashantvc]

We have noticed surge of spam extensions in the marketplace this week. We dialed up the spam detection code, and this is side effect, unfortunately.

Please note that the team is working tirelessly to restore the service, and we apricate your patience

[sathaker]

Hi @estruyf @tronical @gareth-rees

We have shipped the fix and you should be able to update your extension as desired. Feel free to retry and confirm here. Thank you for your patience.

[estruyf]

Thanks @sathaker, I can confirm that the APIs are working again.

[gareth-rees]

@sathaker @prashantvc I was able to update the Time Travel Debug for C/C++ extension. Thank you for fixing the problem.

[dimacodota]

We're running into the same issue, when trying to update the Tabnine extension

[Vaporizer-dev]

Hi @prashantvc I'm having the same issue, unable to upload vscode theme like before.(extension has suspicious content...)

[Lakshmikanth2001]

Even I am facing the same error

Extension validation error

Your extension has suspicious content. Please fix your extension metadata, or contact support if you need assistance.

githooks-0.1.3.zip

please help me out

[anupkmr03]

@Lakshmikanth2001 As @prashantvc mentioned we enabled the spam detection code, and this is side effect. If you are still facing the problem, please let us know we will investigate further.

[Lakshmikanth2001]

no the issue is resolved thank you

[anupkmr03]

Thanks @Lakshmikanth2001 for the update closing the issue.