chore: update npm provenance repository

[StevenMcClankerton]

Summary

• update package repository metadata from prisma/prisma to prisma/orm
• keep npm provenance metadata aligned with the renamed GitHub repository on the v7 release line

Validation

• verified no package manifests reference https://github.com/prisma/prisma.git
• parsed all 173 package manifests as JSON
• git diff --check

Summary by CodeRabbit

• Chores
  • Updated repository links across Prisma packages to point to the new ORM repository.
  • No functional behavior or public APIs changed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: fa323101-41a1-413d-bdc2-2b2220b616d7

📥 Commits

Reviewing files that changed from the base of the PR and between e92bc46 and 72c040f.

📒 Files selected for processing (47)

• packages/adapter-better-sqlite3/package.json
• packages/adapter-d1/package.json
• packages/adapter-libsql/package.json
• packages/adapter-mariadb/package.json
• packages/adapter-mssql/package.json
• packages/adapter-neon/package.json
• packages/adapter-pg/package.json
• packages/adapter-planetscale/package.json
• packages/adapter-ppg/package.json
• packages/bundled-js-drivers/package.json
• packages/cli/package.json
• packages/client-common/package.json
• packages/client-engine-runtime/package.json
• packages/client-generator-js/package.json
• packages/client-generator-registry/package.json
• packages/client-generator-ts/package.json
• packages/client-runtime-utils/package.json
• packages/client/package.json
• packages/config/package.json
• packages/credentials-store/package.json
• packages/debug/package.json
• packages/dmmf/package.json
• packages/driver-adapter-utils/package.json
• packages/engines/package.json
• packages/fetch-engine/package.json
• packages/generator-helper/package.json
• packages/generator/package.json
• packages/get-dmmf/package.json
• packages/get-platform/package.json
• packages/instrumentation-contract/package.json
• packages/instrumentation/package.json
• packages/integration-tests/package.json
• packages/internals/package.json
• packages/json-protocol/package.json
• packages/migrate/package.json
• packages/nextjs-monorepo-workaround-plugin/package.json
• packages/param-graph-builder/package.json
• packages/param-graph/package.json
• packages/prisma7/package.json
• packages/query-plan-executor/package.json
• packages/schema-files-loader/package.json
• packages/sqlcommenter-query-insights/package.json
• packages/sqlcommenter-query-tags/package.json
• packages/sqlcommenter-trace-context/package.json
• packages/sqlcommenter/package.json
• packages/ts-builders/package.json
• packages/type-benchmark-tests/package.json

Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request updates repository URLs in 47 package manifests from prisma/prisma.git to prisma/orm.git. No public entities or runtime behavior changed.

Changes

Repository metadata

Layer / File(s)	Summary
Update package repository URLs packages/*/package.json	The affected package manifests now reference https://github.com/prisma/orm.git in their repository metadata.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 72c04

This change updates npm repository metadata to match the renamed GitHub repository without changing runtime behavior. No actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: aqrln

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the repository metadata update and its npm provenance purpose.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (47 skipped: 47 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/update-npm-provenance-v7

---

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