magento.watch

Reviewed 9m ago.

tools

13 tools scanned

metadata

scanned

No findings.

• get_version

  Get detailed information about a specific Magento/Adobe Commerce version including release date, EOL date, system requirements, and a security summary: `security.fixedBy` (security fixes already included in this version) and `security.vulnerableTo` (open bulletins that still need an upgrade or an isolated patch)

• get_all_versions

  Get all versions for a distribution with their lifecycle information. Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVersion` and `statusLabel` describe the support lifecycle only, so a supported version can still have open bulletins. Call check_version_security for the remedies.

• get_supported_versions

  Get only currently supported versions (not EOL, not future releases). Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVersion` and `statusLabel` describe the support lifecycle only, so a supported version can still have open bulletins. Call check_version_security for the remedies.

• get_eol_versions

  Get versions that have reached end-of-life. Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVersion` and `statusLabel` describe the support lifecycle only, so a supported version can still have open bulletins. Call check_version_security for the remedies.

• check_compatibility

  Check if a specific PHP, MySQL, or other dependency version is compatible with a Magento version

• get_latest_version

  Get the latest stable version for a distribution. Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVersion` and `statusLabel` describe the support lifecycle only, so a supported version can still have open bulletins. Call check_version_security for the remedies.

• get_security_bulletins

  List Adobe/Magento security bulletins (CVEs), optionally filtered by severity or publish date. Use this to list critical bulletins since a given date, or to survey what has been disclosed.

• get_security_bulletin

  Get one security bulletin by id, including a plain-text summary, its CVEs, severity, and which versions per distribution contain the fix. Use this when the user names a specific bulletin or asks which patch fixes a given CVE.

• check_version_security

  Check whether a specific Magento/Adobe Commerce version is vulnerable to known security bulletins, and which version fixes it. A version is also vulnerable when the only remedy from Adobe is an isolated patch applied on top of that base release; fixedIn is then null. This is the tool to call when a user asks "is my Magento vulnerable" or "which patch fixes CVE-...".

• find_patch

  Find Adobe Quality Patches Tool (QPT) patches for a Magento Open Source or Adobe Commerce version. With only distribution and version it lists every applicable patch. Add query (symptoms, error text, feature words or a patch id like ACSD-56760), modules (e.g. "catalog", "module-sales") or categories (QPT names like "Admin", "Catalog/Product") to get a ranked list with a 0-100 relevance score and the signals that matched. Covers quality patches only; for security fixes use check_version_security. List mode can return several hundred hits; pass query, modules or categories to rank and limit. Mage-OS is not a QPT target and always returns status "unknown".

• get_patch

  Get one Quality Patches Tool patch by id (e.g. "ACSD-56760") with every file variant, its Composer constraint, resolved applicable versions per distribution, modified files, prerequisites, documentation fields and the raw patch URL.

• find_upstream_fix

  Community fixes merged into magento/magento2 after a release line was cut, with per-version applicability from git apply checks; not Adobe Quality Patches, for those use find_patch. With only distribution and version it lists, newest first, every upstream fix whose code applies cleanly to that version and that the version does not contain yet. Add query (symptoms, error text, feature words or an id like magento2-40867), modules or categories (QPT category names like "GraphQL", "Catalog/Product") to get a ranked list with a 0-100 relevance score and the signals that matched. fixedIn filters by the first release that contains the fix (null for fixes not in any release yet). Mage-OS always returns status "unknown"; a version outside the checked release tags returns status "unknown-version".

• get_upstream_fix

  Community fixes merged into magento/magento2 after a release line was cut, with per-version applicability from git apply checks; not Adobe Quality Patches, for those use find_patch. Get one upstream fix by id (e.g. "magento2-40867") with its pull request, linked issues, first release containing it, per-tag code match, affected versions, touched packages and files, labels and triage scores. Pass version, and optionally distribution, to get the code match for that version and the Composer bundle URL when the fix applies to it.