Free Connect EOS evidence self-check

Inspect what your artifacts say—before admin messaging does.

For teams maintaining Jira or Confluence Marketplace apps. Check an atlassian-connect.json and optional Forge manifest.yml. See what is observed, missing, invalid, or still needs vendor-controlled verification.

0files uploaded
1 MiBmaximum per file
7manual evidence gates

Local input

Run the evidence check

Selected file contents remain in this tab. The generated report is yours to review and redact.

01 / ConnectRequired

Connect descriptor

Select the exact atlassian-connect.json you want to inspect.

02 / ForgeOptional

Forge manifest

Add the corresponding manifest.yml when available.

Maximum 1 MiB per file

Waiting for local evidence

No upload. No readiness score. Just traceable observations.

The result will separate supplied-file facts from checks only your team can perform.

Scope, clearly

What this does—and what it refuses to guess.

Does a clean self-check confirm what customers currently see?

No. Published versions, Developer Canary banner behavior, guide links, and public communication surfaces require separate vendor-controlled evidence.

Are my files uploaded to Provelity?

Provelity application code has no account, analytics, upload endpoint, or application-managed browser storage. The hosting/security provider may process ordinary request metadata and set a short-lived security cookie when the page loads. Selected file contents and generated reports are processed by the checker in this tab and are not intentionally transmitted by the application.

Is this a migration-readiness or Marketplace-approval tool?

No. It inventories supported evidence in supplied files. It does not assess architecture, module equivalence, runtime, data, effort, security, legal compliance, or approval.

What happens if I request a fit check?

Email is optional. Provelity uses the contact, public app, and business details you choose to send only to respond to the inquiry. Do not attach source files, manifests, reports, credentials, tenant/customer data, or screenshots. Use the same email route to request deletion; any accepted engagement receives its evidence-transfer and retention terms separately.