Skip to content

MP periodic scan #11836

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
NicoletaComan wants to merge 1 commit into
base: development
Choose a base branch
from
Open

MP periodic scan #11836

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions content/en/docs/marketplace/manage-content/upload-content/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,8 +198,6 @@ Note that it may take a short while before the component becomes visible.

For details on the approval process, refer to [Governance Process](/appstore/submit-content/governance-process/).

Every new public component or component version is scanned through [QSM](/appstore/partner-solutions/qsm/), and, if no vulnerabilities are found, it is automatically uploaded. In case of vulnerabilities, Mendix manually checks the component or component version.

## Updating Existing Marketplace Content {#updating}

After you publish a component to the Mendix Marketplace, it is your responsibility to make sure that the component is updated on a regular cadence. This is important to ensure compatibility with the latest versions of dependencies, especially Mendix Studio Pro. It is also required so Mendix can ensure the quality of components in the Marketplace.
Expand Down Expand Up @@ -247,6 +245,12 @@ These fields cannot be edited while updating a component:
* **Release Version**
* **License Type**

## Scanning Components

Mendix scans every new public component or component version through [QSM](/appstore/partner-solutions/qsm/). If no vulnerabilities are found, the component or version is automatically uploaded. If vulnerabilities are found, the component or version is declined, and its developer must fix the vulnerabilities and resubmit it for review.

On top of that, Mendix performs a weekly scan of all latest versions of all Marketplace components. If no vulnerabilities are found, a badge is displayed on the **Releases** tab of the component's Marketplace page. If vulnerabilities are found, the component owner is notified via email, with the option to publish a security fix. If vulnerabilities are not fixed within 30 days, the component is deprecated.

## Releasing Security Fixes {#security-fixes}

You can highlight releases that include security fixes. This allows component users to see which older versions are not safe, as well as which version they need to update to in order to solve security issues.
Expand Down
8 changes: 8 additions & 0 deletions content/en/docs/releasenotes/marketplace/general-marketplace/2026.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,14 @@ weight: 1
numberless_headings: true
---

## September 2026

### September xx, 2026
Comment thread
NicoletaComan marked this conversation as resolved.

#### New Features

* Mendix now performs weekly scans of the latest version of every Marketplace component, thus ensuring that Mendix Marketplace remains a secure and trustworthy platform. If no vulnerabilities are found, a badge is displayed on the **Releases** tab of the component's Marketplace page. If, however, any vulnerabilities are identified, the component owner is notified via email, with the option to publish a security fix. The same information is presented under the form of a Mendix Portal notification. If vulnerabilities are not fixed within 30 days, the component is deprecated.

## August 2026

### August 27, 2026
Expand Down