OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
Issue endpoints return paginated JSON with state, labels, timestamps and bodies. Pull requests also appear as issues and must be distinguished by their pull_request field.
GitHub issue REST operations ↗
List repository issues, since and pagination · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
Issue endpoints return paginated JSON with state, labels, timestamps and bodies. Pull requests also appear as issues and must be distinguished by their pull_request field.
GitHub issue REST operations ↗
List repository issues, since and pagination · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
Issue list endpoints support since, labels, state and sorting. These filters do not establish SQL joins over the service.
GitHub issue REST operations ↗
List repository issues, since and pagination · Checked 2026-10-16
Access cost barrier -
-
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
Authenticated API budgets are documented, but the reviewed route sources do not establish a complete fixed-fee/minimum-plan statement for this portfolio.
GitHub REST rate limits ↗
Primary installation limits and secondary limits · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
Customers install a GitHub App and choose repositories and permissions. Organization policies can require administrator approval; a Marketplace listing is separate from ordinary app installation.
GitHub App creation and installation ↗
Installing apps and repository permissions · Checked 2026-10-16
Downstream permission -
-
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
Applicable third-party processing, AI-use and redistribution terms require a separate contractual review.
GitHub App creation and installation ↗
Installing apps and repository permissions · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
Repository issue operations document create and update, constrained by Issues permissions and the installation’s repository access.
GitHub create and update issue operations ↗
Create an issue and update an issue · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
Customers can build or choose applications using the documented API and the disclosed authorization route.
GitHub App creation and installation ↗
Installing apps and repository permissions · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
Issue webhook activity supports refresh, while updated-since issue queries provide overlapping polling. Failed deliveries are not automatically redelivered by GitHub.
GitHub issue webhook events ↗
Issues webhook and action types · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
Authenticated requests commonly have a 5,000-per-hour primary limit; installation scaling and Enterprise exceptions differ. Secondary limits and reset/retry headers must also be respected.
GitHub REST rate limits ↗
Primary installation limits and secondary limits · Checked 2026-10-16
CDC and deletion capture -
-
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
The reviewed issue webhook catalog establishes event actions, but complete issue deletion and transfer coverage for this selected scope remains unresolved.
GitHub issue webhook events ↗
Issues webhook and action types · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
GitHub supports explicit redelivery of recent failed deliveries; this is delivery recovery, not a durable ordered change stream or whole-history checkpoint.
GitHub webhook delivery recovery ↗
Redelivering failed deliveries · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
REST issue records are portable JSON. Git mirror backups preserve Git history, while issues, discussions, release assets and other hosted metadata need separate extraction.
GitHub repository backup scope ↗
Mirror clone and limits of backups · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
The reviewed extraction guide does not establish contractual retrieval rights after cancellation.
GitHub repository backup scope ↗
Mirror clone and limits of backups · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
REST issue records are portable JSON. Git mirror backups preserve Git history, while issues, discussions, release assets and other hosted metadata need separate extraction.
GitHub repository backup scope ↗
Mirror clone and limits of backups · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
GitHub App creation and installation ↗
Installing apps and repository permissions · Checked 2026-10-16
Rights to custom logic -
-
GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.
Native workflow ownership, reusable export and independent execution rights remain unresolved.
GitHub App creation and installation ↗
Installing apps and repository permissions · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Customers install a GitHub App and choose repositories and permissions. Organization policies can require administrator approval; a Marketplace listing is separate from ordinary app installation.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Issue endpoints return paginated JSON with state, labels, timestamps and bodies. Pull requests also appear as issues and must be distinguished by their pull_request field. Issue list endpoints support since, labels, state and sorting. These filters do not establish SQL joins over the service.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized application | OAuth 2.0 | Integration provider | No | customer authorization | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Authenticated API budgets are documented, but the reviewed route sources do not establish a complete fixed-fee/minimum-plan statement for this portfolio.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Repository issue operations document create and update, constrained by Issues permissions and the installation’s repository access.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Issue webhook activity supports refresh, while updated-since issue queries provide overlapping polling. Failed deliveries are not automatically redelivered by GitHub. Authenticated requests commonly have a 5,000-per-hour primary limit; installation scaling and Enterprise exceptions differ. Secondary limits and reset/retry headers must also be respected.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. The reviewed issue webhook catalog establishes event actions, but complete issue deletion and transfer coverage for this selected scope remains unresolved. | GitHub issue webhook events ↗Issues webhook and action typesChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. GitHub supports explicit redelivery of recent failed deliveries; this is delivery recovery, not a durable ordered change stream or whole-history checkpoint. | GitHub webhook delivery recovery ↗Redelivering failed deliveriesChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
REST issue records are portable JSON. Git mirror backups preserve Git history, while issues, discussions, release assets and other hosted metadata need separate extraction.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. Issue endpoints return paginated JSON with state, labels, timestamps and bodies. Pull requests also appear as issues and must be distinguished by their pull_request field. | GitHub issue REST operations ↗List repository issues, since and paginationChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. Issue endpoints return paginated JSON with state, labels, timestamps and bodies. Pull requests also appear as issues and must be distinguished by their pull_request field. | GitHub issue REST operations ↗List repository issues, since and paginationChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. Issue list endpoints support since, labels, state and sorting. These filters do not establish SQL joins over the service. | GitHub issue REST operations ↗List repository issues, since and paginationChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. Customers install a GitHub App and choose repositories and permissions. Organization policies can require administrator approval; a Marketplace listing is separate from ordinary app installation. | GitHub App creation and installation ↗Installing apps and repository permissionsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. Authenticated API budgets are documented, but the reviewed route sources do not establish a complete fixed-fee/minimum-plan statement for this portfolio. | GitHub REST rate limits ↗Primary installation limits and secondary limitsChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. Applicable third-party processing, AI-use and redistribution terms require a separate contractual review. | GitHub App creation and installation ↗Installing apps and repository permissionsChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. Repository issue operations document create and update, constrained by Issues permissions and the installation’s repository access. | GitHub create and update issue operations ↗Create an issue and update an issueChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. Customers can build or choose applications using the documented API and the disclosed authorization route. | GitHub App creation and installation ↗Installing apps and repository permissionsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. Issue webhook activity supports refresh, while updated-since issue queries provide overlapping polling. Failed deliveries are not automatically redelivered by GitHub. | GitHub issue webhook events ↗Issues webhook and action typesChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. Authenticated requests commonly have a 5,000-per-hour primary limit; installation scaling and Enterprise exceptions differ. Secondary limits and reset/retry headers must also be respected. | GitHub REST rate limits ↗Primary installation limits and secondary limitsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. REST issue records are portable JSON. Git mirror backups preserve Git history, while issues, discussions, release assets and other hosted metadata need separate extraction. | GitHub repository backup scope ↗Mirror clone and limits of backupsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. The reviewed extraction guide does not establish contractual retrieval rights after cancellation. | GitHub repository backup scope ↗Mirror clone and limits of backupsChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights). | GitHub App creation and installation ↗Installing apps and repository permissionsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. Native workflow ownership, reusable export and independent execution rights remain unresolved. | GitHub App creation and installation ↗Installing apps and repository permissionsChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness. REST issue records are portable JSON. Git mirror backups preserve Git history, while issues, discussions, release assets and other hosted metadata need separate extraction. | GitHub repository backup scope ↗Mirror clone and limits of backupsChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Applicable downstream processing and redistribution terms
- Post-cancellation retrieval rights
- Native workflow artifact ownership and independent execution
- Whole-product completeness beyond the declared objects and routes
- Complete commercial entitlement for the assessed portfolio
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.