legal: record exact standalone artifact inspection

[eXPerience83]

Scope

Record a bounded inspection of the exact AMD64 and ARM64 release assets currently distributed for GitHub CLI, Codex CLI, ttyd, mise and uv.

Results

• every asset was downloaded from its pinned URL and matched the repository-controlled SHA-256;
• GitHub CLI archives contain a LICENSE whose content exactly matches the preserved version-specific repository license;
• Codex archives contain one executable and no separate legal file, while the exact-tag LICENSE and NOTICE are preserved by the image;
• ttyd and mise are raw executable assets, so no separate archive member can carry their license; their exact-tag repository licenses are preserved;
• uv archives contain two executable files and no legal member; the exact-version Apache-2.0 and MIT texts are preserved;
• AMD64 and ARM64 packaging produced identical legal-file findings for every component.

The final PR contains only the Markdown/JSON evidence and a documentation link. The temporary inspector and workflow used to produce the evidence have been removed.

Boundaries

This report is tied to the exact pinned versions and hashes. It does not scan arbitrary binaries or infer transitive dependency licenses. Repeat it when an upstream changes its distribution packaging.

Refs #26

[coderabbitai]

Warning

Review limit reached

@eXPerience83, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 50 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 1f4d3686-b637-4061-801b-236d271e02c1

📥 Commits

Reviewing files that changed from the base of the PR and between 31f67e2 and 83b3ef0.

📒 Files selected for processing (3)

• third_party/README.md
• third_party/standalone-artifact-inspection.json
• third_party/standalone-artifact-inspection.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 83b3ef0f60

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".