Atlassian App Change Impact Auditor

Find Connect-to-Forge migration blockers before they become production incidents.

This Actor cross-checks an atlassian-connect.json descriptor, a Forge manifest.yml, and optional source files. It returns evidence-linked migration findings, module coverage, deprecated REST API usage, permission and remote mismatches, a readiness score, and CI-ready release artifacts.

It is designed for Marketplace vendors, solution partners, and teams maintaining private Jira, Jira Service Management, or Confluence apps as Atlassian Connect approaches end of support in December 2026.

What it checks

• Connect and Forge app-key, licensing, base URL, and remote consistency.
• Missing or invalid Connect JWT and lifecycle configuration.
• Retained connectModules and current Connect-to-Forge module mappings.
• Modules and web-item locations with no generally available Forge equivalent.
• Migration identity requirements such as same-key modules and migratedFromConnect.
• Jira issue glance to issue context migration.
• Confluence macro and content-property compatibility risks.
• Forge remote keys, HTTPS URLs, data-residency declarations, and token scopes.
• Source calls matched against 69 deprecated operations from six official Atlassian OpenAPI documents, snapshot on 2026-07-11.
• Removed Jira pagination/search APIs, legacy user identifiers, dynamic Connect modules, AUI CDN, Connect frameworks, and removed Atlaskit icon imports.

Each finding includes a stable rule ID, severity, confidence, file and line when available, recommended action, deadline when known, and a direct Atlassian documentation URL.

Input options

You can use any combination of:

1. A parsed connectDescriptor JSON object.
2. forgeManifestYaml text.
3. uploadedFiles from Apify's file uploader or authorized public HTTPS URLs.
4. Inline sourceFiles for API, CLI, MCP, and CI workflows.

Uploaded ZIP projects are expanded with strict entry-count, per-file, and total-size limits. Path traversal, symlinks, encrypted entries, oversized entries, private-network URLs, credential-bearing URLs, and non-HTTP protocols are rejected. node_modules, build output, vendor directories, tests, fixtures, and Markdown are excluded from production source findings by default.

Customer source code is parsed as bounded text and is never installed or executed.

Quick start

{
  "connectDescriptor": {
    "key": "com.example.app",
    "name": "Example",
    "baseUrl": "https://app.example.com",
    "authentication": { "type": "jwt" },
    "lifecycle": { "installed": "/installed" },
    "enableLicensing": true,
    "scopes": ["READ"],
    "modules": {
      "jiraIssueGlances": [{ "key": "summary", "url": "/summary" }]
    }
  },
  "forgeManifestYaml": "app:\n  id: ari:cloud:ecosystem::app/...\n  connect:\n    key: com.example.app\n    remote: backend\n  licensing:\n    enabled: true\nmodules:\n  jira:issueContext:\n    - key: summary\n      resource: main\nremotes:\n  - key: backend\n    baseUrl: https://app.example.com\n    operations: [compute]\npermissions:\n  scopes: []\n",
  "releaseGate": {
    "enabled": true,
    "failOnSeverity": "high",
    "failOnNotAvailableModule": true
  }
}

The report is written before a configured release gate fails the run, so CI can still retrieve all evidence.

Outputs

• Default Dataset: one complete structured audit report.
• OUTPUT: validated run summary with readiness score, gate status, and billing evidence.
• REPORT.md: human-readable migration plan.
• REPORT.sarif: findings for code scanning and engineering tools.
• junit.xml: findings for CI test-report consumers.

Severity and confidence

Only deterministic, high-confidence conditions are treated as blockers. When Atlassian documentation sources conflict or a value is dynamically constructed, the Actor reports a review finding instead of claiming certainty. Official changelogs and current module references take priority over older capability tables.

The API/CLI default release gate fails on high or critical findings and on modules currently classified as not available. Set releaseGate.enabled to false for an advisory report. The Store's prefilled demonstration input uses advisory mode so it can return a complete example report successfully; enable the gate explicitly for CI enforcement.

Billing

Launch Pay Per Event pricing:

• apify-actor-start: $0.00005 once per run, charged automatically by Apify.
• app-audited: $0.49 once after a valid structured report is produced.

Invalid input, blocked file retrieval, unsafe archives, and parsing failures do not emit app-audited. The removable synthetic apify-default-dataset-item event must stay unpriced. Platform compute, storage, and transfer usage is passed through to the caller so failed or adversarial uploads cannot create unbounded author cost.

Set a positive run-level maxTotalChargeUsd when invoking the Actor through API or MCP. Do not set zero as a limit.

Privacy and security

The Actor does not require an Atlassian account, site URL, API token, session cookie, or Marketplace credential. It does not log or publish source-file bodies. Output evidence is limited to rule-relevant API paths, module keys, import paths, and configuration values. Named storage contains billing idempotency markers only; the supplied source remains in the run input/storage controlled by Apify retention settings.

Do not include secrets in source input. Remove credentials, private keys, production tokens, and customer data before upload.

Limitations

• This is deterministic static analysis, not Atlassian certification, legal advice, or a guarantee that migration will succeed.
• Dynamically built URLs, runtime module registrations, tenant data migrations, feature flags, and behavior inside Atlassian sites can require manual testing.
• The bundled official-rule snapshot is versioned. Re-run after Actor updates and Atlassian platform changes.
• The Actor is an independent developer tool and is not affiliated with, endorsed by, or sponsored by Atlassian.

Atlassian, Jira, Confluence, and Forge are trademarks of Atlassian and/or its affiliates.