fix: align package repository metadata

[FranciscoMoretti]

Summary

• align publishable package repository metadata with FranciscoMoretti/chat-js
• use npm-normalized git+https repository URLs for trusted publishing

Validation

• parsed updated package JSON files

---

Summary by cubic

Aligned repository metadata in packages/cli and packages/registry with FranciscoMoretti/chat-js to fix npm links and support trusted publishing.
Switched to npm-normalized git+https repository URLs and corrected homepage/issues URLs.

^{Written for commit 008ea0f. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
chat-js-site	Ready	Preview, Comment	Jul 3, 2026 9:58am
sparka	Ready	Preview, Comment	Jul 3, 2026 9:58am

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 25 seconds

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 48327e69-1bda-4004-b9c7-b9e7afd1fe01

📥 Commits

Reviewing files that changed from the base of the PR and between 41e4704 and 008ea0f.

📒 Files selected for processing (2)

• packages/cli/package.json
• packages/registry/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/fix-cli-repository-url

---

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.}

[greptile-apps]

Greptile Summary

This PR corrects the repository metadata in the two published packages (packages/cli and packages/registry) by fixing the GitHub username casing (franciscomoretti → FranciscoMoretti) and switching the repository.url field to the npm-normalized git+https:// scheme.

• Both packages/cli/package.json and packages/registry/package.json have their repository.url, homepage, and bugs.url fields updated consistently.
• No logic, dependencies, or runtime code is affected; the change is purely cosmetic/metadata.

Confidence Score: 5/5

Metadata-only change with no impact on runtime behavior or dependencies; safe to merge.

Both files only update the repository.url, homepage, and bugs.url fields. The fix is consistent across both packages, no other package.json files in the repo still carry the old lowercase URL, and no logic or dependency changes are involved.

No files require special attention.

Important Files Changed

Filename	Overview
packages/cli/package.json	Repository URL, homepage, and bugs URL updated to correct casing and git+https scheme — no functional changes.
packages/registry/package.json	Same metadata corrections as the CLI package — git+https URL and correct username casing applied consistently.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[npm publish] --> B{repository.url}
    B -->|before| C["https://github.com/franciscomoretti/chat-js.git\n(lowercase, plain https)"]
    B -->|after| D["git+https://github.com/FranciscoMoretti/chat-js.git\n(correct casing, npm-normalized)"]
    D --> E[npmjs.com shows correct repo link]
    D --> F[Trusted publishing resolves correct owner]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[npm publish] --> B{repository.url}
    B -->|before| C["https://github.com/franciscomoretti/chat-js.git\n(lowercase, plain https)"]
    B -->|after| D["git+https://github.com/FranciscoMoretti/chat-js.git\n(correct casing, npm-normalized)"]
    D --> E[npmjs.com shows correct repo link]
    D --> F[Trusted publishing resolves correct owner]

Loading

_{Reviews (1): Last reviewed commit: "fix: align package repository metadata" | Re-trigger Greptile}

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}