generated: '2026-09-07'
method: searched
source: >-
  https://status.eclipse.org, https://github.com/eclipse-openvsx/openvsx/releases,
  https://www.eclipse.org/projects/handbook/, https://www.eclipse.org/security/policy/,
  and the `deprecated: true` flags in the 18 harvested first-party OpenAPIs.
provider: Eclipse Foundation
providerId: eclipse
description: >-
  Versioning, deprecation, release and availability posture for the Eclipse Foundation API surface.
  The Foundation runs a mature project lifecycle process for its OPEN SOURCE PROJECTS (the Eclipse
  Project Handbook defines Incubation / Mature / Archived phases and a formal release review), but
  publishes no lifecycle policy for its own HOSTED WEB APIs. Those are two different things, and
  the distinction is the main finding here.

status_page:
  present: true
  url: https://status.eclipse.org
  http_status: 200
  verified: '2026-09-07'
  scope: >-
    Covers Foundation infrastructure — accounts, GitLab, Jenkins/CI, download servers, the website
    and Open VSX. Incident history and component-level status are published.
  machine_readable: false
  note: >-
    No statuspage.io-style JSON endpoint. /api/v2/status.json and /api/v2/summary.json return the
    page's HTML shell (200), so availability is human-readable only — an agent cannot poll it.

versioning:
  scheme: unversioned-paths
  detail: >-
    No API on the surface carries a version segment in its base path. The single exception is Open
    VSX, which ships `/api/v2/-/query` alongside `/api/-/query`. Specification versions in
    info.version are inconsistent across the estate (1.0, 1.0.0, 1.1.0 all in use) and are not tied
    to a published release cadence for the Foundation IT APIs.
  runtime_version_endpoint: 'GET https://open-vsx.org/api/version (getRegistryVersion)'
  breaking_change_policy: none published
  note: >-
    Because paths are unversioned and no breaking-change policy exists, a consumer of the
    api.eclipse.org APIs has no contractual notice mechanism for an incompatible change.

deprecation:
  policy_published: false
  sunset_header: false
  deprecation_header: false
  rfc8594: false
  detail: >-
    No deprecation policy, no notice period, no RFC 8594 Sunset or Deprecation response header on
    any of the 294 operations. What the Foundation DOES do is flag deprecated operations in the
    specification itself — 5 of them — which is a real, machine-readable signal even without a
    surrounding policy.
  deprecated_operations:
    - api: Eclipse Projects PMI API
      operation: 'GET /api/simultaneous_release (FetchSimultaneousReleases)'
      spec: openapi/eclipse-projects-pmi-api-openapi.yml
      replacement: not stated
    - api: Eclipse Projects PMI API
      operation: 'GET /api/simultaneous_release/{simrel} (RetrieveSimultaneousRelease)'
      spec: openapi/eclipse-projects-pmi-api-openapi.yml
      replacement: not stated
    - api: Eclipse Membership Portal API
      operation: 'GET /working_groups (getWorkingGroups)'
      spec: openapi/eclipse-membership-portal-api-openapi.yml
      replacement: >-
        Superseded in practice by the standalone Working Groups API at
        https://api.eclipse.org/working-groups, which is published as its own specification.
    - api: Eclipse Membership Portal API
      operation: 'GET /working_groups/{documentID} (getWorkingGroup)'
      spec: openapi/eclipse-membership-portal-api-openapi.yml
      replacement: See above.
    - api: Open VSX Registry API
      operation: 'POST /api/-/query (postQuery)'
      spec: openapi/eclipse-open-vsx-registry-api-openapi.yml
      replacement: 'GET /api/v2/-/query (getQueryV2)'
  count: 5

releases:
  cadence:
    - estate: Eclipse Open VSX
      cadence: Tagged GitHub releases, roughly every 1-3 weeks, semver, three separately versioned lines (server, webui, cli).
      source: https://github.com/eclipse-openvsx/openvsx/releases
      current: v1.1.2 (2026-08-20)
      lifecycle_phase: >-
        Mature — Eclipse Open VSX graduated from Incubation to the Mature phase in June 2026 under
        the Eclipse Project Handbook process.
    - estate: Eclipse Foundation IT APIs
      cadence: none published
      source: https://gitlab.eclipse.org/eclipsefdn/it/api
      note: >-
        Source repositories are public on gitlab.eclipse.org and several specs name their issue
        tracker as info.contact.url, but no dated release feed or changelog is published for the
        hosted APIs themselves.

sla:
  published: false
  detail: >-
    No availability target, uptime commitment or support-response SLA is published for any API.
    Consistent with a non-profit publishing free, unmetered APIs (see plans/eclipse-plans-pricing.yml).

support:
  issue_trackers:
    - https://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-info-api/-/issues
    - https://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-profile-api/-/issues
    - https://gitlab.eclipse.org/eclipsefdn/it/api/git-eca-rest-api/-/issues
    - https://gitlab.eclipse.org/eclipsefdn/software-dev
    - https://github.com/eclipse-openvsx/openvsx/issues
  note: >-
    Named directly in info.contact.url of the Info, Profile, Git ECA and Membership Portal
    specifications — a real, per-API support path, which is better than the surface's lack of a
    single support portal suggests.
  contact: https://www.eclipse.org/org/foundation/contact.php

security_lifecycle:
  vulnerability_policy: https://www.eclipse.org/security/policy/
  known_vulnerabilities: https://www.eclipse.org/security/known/
  see: security/eclipse-vulnerability-disclosure.yml