RepoPilot

prisma / orm

Search prisma/orm

GitHub

Code

How prisma/orm is laid out, and where to start for common changes.

A
Architecture grade
score 100/100
0
Import cycles
lower is better
83
Files mapped
11 imports between them
100%
Layering
of imports point one way

From the map of which files import which, built when the code was last read in full. It shows what depends on what, not a reading order.

Module map

Shade by
Standalonepackages1985 files · 100+ commitsexamples447 files · 100+ commitsapps24 files · 73 commits

3 modules, 0 links. A link means one module imports another; thicker lines mean more imports. Links come from 83 of 2,590 source files, so the real counts are higher. Select a module to trace it: blue lines go to what it uses, orange lines come from what uses it.

packages198500100+Standalone
examples44700100+Standalone
apps240073Standalone

Where to start reading

  1. Repository root
  2. Repository root
  3. Likely public API
  4. Likely start-up file
  5. Likely start-up file
  6. Suggested starting pointAI
  7. Suggested starting pointAI
  8. Suggested starting pointAI

Find files for a task

AI

Add a new ORM extension feature

  • Implement hook interface defined in packages/0-shared/extension-author-tools/README.md for query interception.
  • Add skill documentation in skills-contrib/ folder describing usage patterns and API.

Document architectural decision or design pattern

  • Create design-notes.md or README.md in the relevant projects/[feature-name]/ folder.
  • Reference the project in ARCHITECTURE.md under appropriate layer section.
  • Create corresponding skill file in skills-contrib/ if this is a reusable pattern other contributors should learn.

Add a migration or upgrade path for new version

  • Document breaking changes, migration steps, and rollback procedures in README or structured files.

Change the public API

Trace runtime behavior

Add or update tests

Change build or automation

RepoPilot lists up to 500 files, so a file missing here may still exist.

  • Files marked “likely” are guessed from their names.
  • 1 suggested change pattern has no matching file and is left out.

Code quality and hotspots

Largest source files

  • Branch points23 per file on average
  • Code issues0 errors, 34 warnings
  • Largest file579 lines
  • Hotspot load1 high-risk file

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions18 workflows
  • Tests5,993 test filesJest/Vitest · 2.3 test files per source file (file count, not coverage)
  • Dependency updatesCodeQL

Test folders: examples/prisma-8-demo/test · apps/telemetry-backend/test · examples/mongo-demo/test

Hotspots

Files that change often and branch heavily, highest first. Branch points count if, loop, case, catch, ternary, && and || in the file.