Add repository metadata for packages

[gentamura]

Summary

• add a GitHub repository field to each package.json so npm provenance validation succeeds

Testing

• not run (metadata change only)

Summary by CodeRabbit

• Chores
  • Added repository metadata to package manifests across API, Auth, DB, and Types packages for improved package management and discoverability.

[coderabbitai]

Walkthrough

Four package manifest files in the packages directory receive an identical repository metadata field containing the Git URL for the listee-libs repository. No functional or dependency changes are made.

Changes

Cohort / File(s)	Summary
Repository metadata addition packages/api/package.json, packages/auth/package.json, packages/db/package.json, packages/types/package.json	Added repository field with type "git" and URL "https://github.com/listee-dev/listee-libs.git" to all package manifests

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Four folders, one repository true,
Metadata whispers of where code grew,
Each package now knows its GitHub home,
A tidy burrow—no more to roam! 📦✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Add repository metadata for packages" is directly aligned with the changes made in the changeset. The PR adds a repository field containing Git repository information to four package.json files across the monorepo (packages/api, packages/auth, packages/db, and packages/types). The title accurately reflects this primary objective, which is also confirmed in the PR description stating the purpose is to add GitHub repository fields for npm provenance validation. The title is concise, clear, and uses specific descriptive language without vague terms or noise, making it easy for teammates reviewing the repository history to understand the change's intent.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/add-repo-fields

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d91526e and 73eec58.

📒 Files selected for processing (4)

• packages/api/package.json (1 hunks)
• packages/auth/package.json (1 hunks)
• packages/db/package.json (1 hunks)
• packages/types/package.json (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

packages/*/package.json

📄 CodeRabbit inference engine (AGENTS.md)

Reference shared dependencies via the "catalog:" protocol in package manifests

Files:

• packages/api/package.json
• packages/auth/package.json
• packages/db/package.json
• packages/types/package.json

🔇 Additional comments (4)

packages/types/package.json (1)

15-18: Repository metadata correctly added for npm provenance validation.

The repository field is properly formatted and positioned. This enables npm provenance attestation as intended.

packages/db/package.json (1)

15-18: Repository metadata correctly added for npm provenance validation.

The repository field is properly formatted and positioned. Dependencies correctly use the catalog: protocol per guidelines.

packages/api/package.json (1)

15-18: Repository metadata correctly added for npm provenance validation.

The repository field is properly formatted and positioned. Dependencies correctly use workspace:* for internal packages and catalog: for external dependencies per guidelines.

packages/auth/package.json (1)

15-18: Repository metadata correctly added for npm provenance validation.

The repository field is properly formatted and positioned. Dependencies correctly use workspace:^ for internal packages and catalog: for external dependencies per guidelines.

---

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 and usage tips.}