Fixtures

A library catalogue that publishes through the AWS SDK in a clone nobody has installed, which is how a serverless repository is usually first read: there is no node_modules, so every client is any to the checker and none of them can say which package declared it.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's API that publishes through the AWS SDK: plain Express handlers that put events on EventBridge, send to SQS queues and, in two functions kept beside it with their own manifests, publish to SNS and send with version 2 of the SDK.

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

One service publishes the same kind of event from four different kinds of body; another subscribes to what it sends.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

One service publishes to a channel whose name it builds; another subscribes to the three names that publish can actually reach.

expected.channel.closed.tree.txt expected.contracts-report.json expected.doctor.txt expected.link-report.json expected.project-graph.json

One subscription, written once, that reaches three channels — and three @Consumes on the handler that restate what it already says.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

The repo with no broker at all: package.json names @nestjs/common and @nestjs/core and nothing else.

expected.contracts-report.json expected.graph.json expected.link-report.json expected.project-graph.json

Queues, where the channel is the queue name and the job name is metadata.

expected.graph.json

The channel-name resolver, end to end.

expected.contracts-report.json expected.graph.json expected.link-report.json expected.project-graph.json

AmqpConnection.publish(exchange, routingKey, msg) and @RabbitSubscribe, plus a ClientProxy on the RMQ transport — the two ways a Nest repo talks to RabbitMQ, side by side, because the nestjs-rabbitmq adapter owns both.

expected.graph.json

Redis pub/sub, the case with no decorator anywhere: producers are redis.publish(channel, message) calls and consumers have to be found by pairing a subscribe(channel) with the on('message', …) listener on the same connection.

expected.graph.json

The same transport as nest-redis-pubsub, read through the other client of it.

expected.graph.json

The two shapes a description could name only at an argument index, and therefore could not name at all (R86).

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A NestJS gateway and a browser in another repository, joined on nothing but the event names they both write.

expected.channel.updated.tree.txt expected.contracts-report.json expected.link-report.json expected.project-graph.json

A plain socket server and a browser in another repository, each naming the same events on the same namespaces.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A browser that subscribes over server-sent events, a service that publishes, and the whole round trip between them.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A repository whose data libraries are declared and not installed, which is what a stranger's clone is.

expected.graph.json

A data layer written twice: as a module of exported functions (src/orders/orders.repository.ts) and as a class (src/orders/orders.class.ts), with the same four queries in each.

expected.graph.json

A drizzle connection is one object for the whole schema, so nothing in the receiver's type names a table.

expected.graph.json

A knex query starts from the table and then chains, so the call that carries the operation is the last one and the table is in the call the chain started from.

expected.graph.json

knex.raw(sql) takes its statement as text, and what it touches is written in the SQL rather than anywhere the knex descriptor's locators look.

expected.graph.json

Kysely hands out one connection, Kysely<DB>, and every query starts by naming its table in the first argument of selectFrom, insertInto, updateTable or deleteFrom.

expected.graph.json

Cache keys, outgoing addresses and configuration reads.

expected.graph.json

A repository whose SQL goes through its ORM's manager: getKnex() on a MikroORM SqlEntityManager hands back a knex instance, and every query after that call is knex's own.

expected.graph.json

nest-mikro-orm-knex with nothing installed: the same src, and no node_modules.

expected.graph.json

A mongoose model carries two facts at once, and they come from two different places.

expected.graph.json

The types say nothing here, so the table names are read out of the query string and the operation comes from its verb.

expected.graph.json

The table name comes from the property the call was made on, not from a type argument, which is what the receiver-prop override exists for.

expected.graph.json

An ORM reached only through a workspace package: nothing in src imports @prisma/client, and every query goes through @acme/db, which configures one client and re-exports it.

expected.graph.json

Sequelize is called on the model itself rather than through an injected repository, so the receiver is a class of this repository and the only reason the call is data access at all is that the class extends one declared in node_modules/sequelize.

expected.graph.json

The decorated form of a sequelize model, which is how a TypeScript project declares one.

expected.graph.json

Exercises the P03 level‑1 (static) DB path: package known via the declaring node_modules/<pkg> of the receiver's type, entity taken from the type argument of Repository<Entity>, operation taken from the typeorm descriptor.

expected.graph.json

What a data layer nobody has described may and may not be named after.

expected.graph.json

A data layer of the project's own, kept in a workspace package beside the service: api reaches its database only through @acme/db, and @acme/db wraps a driver nothing here describes.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A statement handed to pg that is complete and names no table (R162).

expected.graph.json

A query string that parses, names a table, and opens with no verb the reader knows.

expected.graph.json

A workspace whose Prisma client was never generated, which is what a clone installed with --ignore-scripts is: prisma generate runs from a postinstall hook, so packages/db/generated/prisma does not exist, and nothing links @acme/db into api either.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's circulation service: Lambda functions behind an HTTP API that talk to each other over an EventBridge bus.

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

Lambda functions behind a REST API whose every answer is built by a helper of the project's - respond(status, body) from @acme/http-kit, a shared package the repository declares and nobody installed.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

Lambda handlers kept in functions/, beside the code they share in src/, which is how a serverless project commonly lays itself out (R170).

expected.graph.json

The circulation desk of a lending library as Lambda functions behind a REST API and two SQS queues, written the way a project that keeps its logic apart from its entry points often is: src/operations holds the functions, and each module under src/handlers re-exports some of them, in one of the ways a module can (R168).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

Two repositories: catalogue publishes two APIs on the library's own domain, api.library.example, each under a base path; kiosk calls them at that address (R174).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

Bucket notifications declared through the s3-bucket module's notification submodule and in Terraform's JSON form, a bucket that keeps versions, and the writes P52 named but no fixture made (P56).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

Functions run by what is written to S3 buckets (P52).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A rule that hands events on to another team's bus (R174).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's loans service: a kiosk calling another function through its function URL, and functions whose results and failures the platform hands on to destinations (P54).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's catalogue: two Lambda functions behind an HTTP API, deployed by Terraform written entirely as JSON (*.tf.json), the way a generator writes it.

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

The same kind of service declared through modules: one of the repository's own, the public terraform-aws-modules/lambda/aws and terraform-aws-modules/apigateway-v2/aws, and a module from another repository that the configuration describes.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's circulation service with two APIs created from OpenAPI documents rather than from resources and methods (R174).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's members service: functions run by something other than an API Gateway route, a rule, a queue or a topic (P53), and an IoT rule whose actions write a table, start a workflow and fail over to a queue (P56).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

Lambda handlers whose ways in are declared in Terraform: one aws_lambda_function per handler, and a REST API built resource by resource in front of them.

expected.graph.json

Two repositories: branch declares two HTTP APIs that both answer GET /status, two more whose names are not read that both answer GET /hours, and two application load balancers that both forward GET /health, each to a function of its own, the staff one from two listeners; kiosk calls them (P59, P61).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A write to a table reaches the function its stream runs (P51).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's reading room: borrowers ask a librarian over a WebSocket API (R174).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A small shop's checkout on AWS Lambda, deployed with Terraform, with one state machine, and a trace of one checkout as an OpenTelemetry Lambda layer writes it: what flowatlas observe lays over the map the Terraform and the state machine draw (P107).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's loans service whose repository is the root of a workspace: the functions are in its own src/, and the client they start workflows through is a member in packages/workflows, inside the same directory (R175).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

Lambda handlers each wrapped by a helper that takes the function as a later argument, which is how a project that instruments every handler writes them (R167).

expected.graph.json

Lambda handlers each wrapped by a helper of this repository that the handler calls by another name (R175): taken off a namespace import into a const, imported under a short name, or re-exported by a barrel under a new one.

expected.graph.json

A publisher, its rules and its consumers in three repositories, on a bus a fourth repository owns.

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

Three repositories sharing one REST API: two hang their routes from a point of it the third, a repository of nothing but Terraform, publishes.

expected.contracts-report.json expected.doctor.txt expected.flow.post-loans.tree.txt expected.link-report.json expected.project-graph.json

A lending library's returns service: Lambda functions behind a REST API, joined by SQS queues and an SNS topic.

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A state machine in one repository that invokes functions two other repositories deploy, starts a state machine a third deploys, writes a table of its own, and sends to a queue, a topic and a bus whose subscribers the other repositories declare: the joins P22 makes across repositories by a deployed name, and the ones R169 makes between a step that sends and the subscriber P23 reads.

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's loans service whose handler starts a workflow through a helper that records a run in one call and starts it by the run's id in the next, so the name of what is started is written one call before the call that starts it.

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's loans service whose handlers start the approval workflow and invoke a function through helpers written as functions of a module, not methods of a class: export const startWorkflow = async (stateMachineArn, input) => … and export async function notifyFunction(functionName, event).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's loans service whose handlers start workflows through the project's own helpers rather than the AWS SDK: one helper is a package of this workspace, whose source is read, and one comes from a package that is deliberately not here and is described in flowatlas.config.json.

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's loans API, where the handler behind a route starts the approval workflow and invokes other functions by calling the AWS SDK directly.

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

Three state machine definitions kept as files beside the code that runs with them, in two repositories, and one workflow that starts a workflow in the other.

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

Four state machines deployed with Terraform over the Lambda functions of one lending library, each with its definition written a different way.

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

Two repositories holding the shapes the other fixtures never write down, and one thing none of them has: a recording is not its authority.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

One project, four repositories that call each other.

expected.cli expected.contracts-report.json expected.link-report.json expected.mcp expected.mcp.observed expected.mcp.shapes expected.project-graph.json expected.prompt

Five repositories arranged so that each of the four analytics commands has exactly one thing to find and nothing to guess at.

expected.config.json expected.contracts-report.json expected.cycles.json expected.dead.json expected.hotspots.json expected.link-report.json expected.project-graph.json

A browser annotation that names its service (P127).

expected.contracts-report.json expected.link-report.json expected.project-graph.json

Three services, one repository, two documents, and one channel that joins them.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

Base addresses read from the repositories' own files (P77).

expected.link-report.json expected.project-graph.json

Four repositories that disagree with each other on purpose, so that flowatlas contracts has something true to say and something false it must not say.

expected.cli expected.contracts-report.json expected.contracts.json expected.contracts.md expected.contracts.sarif.json expected.contracts.txt expected.link-report.json expected.project-graph.json

Routes nobody calls, told apart (P91).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

Two services, and only one of them has any source here.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A bookshop of three services - gateway, orders, billing - for flowatlas check --env (P117): whether a version can be deployed against what an environment runs, rather than against main.

expected.cli expected.mcp

Two revisions of one project, for flowatlas diff.

expected.cli expected.mcp

Three services that are wrong in every way flowatlas doctor can name, so that one run over this fixture exercises all five of its sections at once.

expected.contracts-report.json expected.doctor.github.txt expected.doctor.json expected.doctor.reason.txt expected.doctor.sarif.json expected.doctor.txt expected.link-report.json expected.project-graph.json

Three services whose every method logs, counts and reads through a shared helper, so a walk that expands each helper once per caller spends its whole budget on plumbing before a request reaches the service it ends in (P92).

expected.contracts-report.json expected.link-report.json expected.mcp expected.project-graph.json

The bookshop of fixtures/multi-repo (a browser, its gateway, orders and billing) with tags on its services and six architecture rules (P114, P203), for flowatlas rules, the rules section of doctor and the MCP server's check_rules.

expected.cli expected.contracts-report.json expected.link-report.json expected.mcp expected.project-graph.json

One repository, and the whole of the fixture is one sentence: a screen in it asks for an address a route in it answers, and the tool says so.

expected.link-report.json expected.project-graph.json

A package inside a workspace, declaring nothing of its own.

expected.link-report.json expected.project-graph.json

A workspace package imported by its own name, with nothing installed (R152).

expected.link-report.json expected.project-graph.json

A workspace package that reaches its own code through an alias only its own tsconfig defines (R141).

expected.link-report.json expected.project-graph.json

Where a NestJS service's addresses are decided, and what it costs to read the wrong file (R89).

expected.graph.json

The smallest NestJS service the tool reads end to end: three modules, a users controller and its service, wired by injection.

expected.graph.json

A check thrown through a helper (P90): a community library's lending desk (NestJS + TypeORM) with no guard anywhere.

expected.cli expected.contracts-report.json expected.link-report.json expected.mcp expected.project-graph.json

A service whose outgoing requests all go through a client class it wrote itself.

expected.graph.json

One NestJS service, shop, whose repository commits an OpenAPI document it writes by hand (shop/openapi.yaml), for flowatlas spec --against and the "Committed API documents" section of flowatlas contracts (P195).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A NestJS service whose every address begins with a mount the deployment sets, and a browser that asks for those addresses under a base already carrying it.

expected.link-report.json expected.project-graph.json

A NestJS API whose extent must stop at the line the package manager draws (R143).

expected.link-report.json expected.project-graph.json

Injection by token rather than by class: @Inject(CONFIG) and the providers that register those tokens, across six modules.

expected.graph.json

Every kind of way into a NestJS service that is not a plain HTTP route.

expected.graph.json

What a route can really answer with (P87): a library-loans API whose main.ts installs a global ValidationPipe and a global DomainErrorFilter (@Catch(DomainError), answering e.status).

expected.graph.json

What a route fails with once its interceptors have had their say (P207): a bookshop API whose main.ts installs a global ValidationPipe, a global TimeoutInterceptor (the framework's documented one: timeout(5000), then a catchError that turns a TimeoutError into a RequestTimeoutException and hands every other error on) and a global ShopErrorFilter (@Catch(ShopError), answering e.status).

expected.graph.json

What each route can fail with (P68), written on the entry as meta.fails: [{ status, exception, at, file, line, source }], sorted by status.

expected.graph.json

A request whose address is completed by its caller keeps the verb and host its own code states (R161).

expected.graph.json

Exercises the full wrapping layer: middleware, guards, interceptors and pipes applied globally, at class level and at method level, plus a custom @Roles('admin') metadata decorator.

expected.graph.json

A NestJS service whose work is done by module-level functions: no class, no provider, and no entry point naming any of them (R156).

expected.graph.json

A lending library's reminders sent through a chat courier.

expected.graph.json

A data layer nothing recognises, shaped the way the real project shapes one: an abstract base over a driver, a class per collection extending it, and receivers named after the thing stored rather than after the layer.

expected.graph.json

One small NestJS repository, shaped so that every kind of change an incremental rebuild has to answer differently is possible in it.

expected.graph.json

Two classes implement one interface, and each builds its request URL from a parameter and calls itself through this (R158).

expected.graph.json

A scheduled job with the zone it fires in, and the lines each step writes to its log.

expected.graph.json

A NestJS API one of whose members installs Angular (R159, the Angular half of R145).

expected.link-report.json expected.project-graph.json

A NestJS API one of whose members declares React as a devDependency only (R145, the second half of R143).

expected.link-report.json expected.project-graph.json

MongoDB collections named where the code names them: in the driver's chain, and on the repository classes a project writes over it (R165).

expected.contracts-report.json expected.link-report.json expected.project-graph.json

nest-context-path with the environment files a notification service commits: every one of them leaves the mount empty (R144).

expected.link-report.json expected.project-graph.json

nest-mount-empty with one line changed: src/.env.production writes API_CONTEXT_PATH=api (R144).

expected.link-report.json expected.project-graph.json

A service that genuinely stores nothing: two providers, a controller, and a map that lives as long as the process does.

expected.graph.json

Exercises P69: a call in a loop, and calls side by side.

expected.graph.json

A NestJS API that really does run React, in one package of it and nowhere else (R145).

expected.link-report.json expected.project-graph.json

Three services, each guarding its routes a different way, so that one run exercises everything the route audit reads about what stands in front of a route and where it was put (P76).

expected.contracts-report.json expected.link-report.json expected.project-graph.json

Many ways in that fail the same ways (P84): the page ships each failure once.

expected.graph.json

Three Nest controllers whose decorators arrive by three different routes, and one reader that used to read only the first of them.

expected.graph.json

A bot whose handlers are declared with decorators.

expected.graph.json

A service that keeps runtime code in a directory named like tests.

expected.link-report.json expected.project-graph.json

One service, two applications, one address each of them serves (R119).

expected.graph.json

Exercises the P02 type layer: TypeCollector, the registry ids, structuralHash, generics, recursion, the depth cap and the class-validator / class-transformer field meta.

expected.contracts-report.json expected.graph.json expected.link-report.json expected.project-graph.json

An application declared by a chain, which is how a video platform declares its one application and what cost a video platform every route it has.

expected.graph.json

A repository whose routes are declared by where its files are, with Express underneath — Medusa v2 in miniature.

expected.graph.json

An Express service whose framework is declared and not installed, which is what a stranger's clone is.

expected.graph.json

One registration, several addresses, which is legal Express and appears eight times in the repositories the coverage harness measures.

expected.graph.json

An Express service and a browser calling it.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A lending library's loans API in Express, every handler wrapped by a helper that takes the function as a later argument: the HTTP side of R167, read by the same rule as a Lambda handler.

expected.graph.json

A named handler handed to a wrapper the repository declares itself, which is how a video platform writes nearly every route it has.

expected.graph.json

One Fastify service, read by the same table row as Express and Koa.

expected.graph.json

One repository serving routes from two frameworks, and a browser calling both.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

Koa applications mounted inside another by a helper, which is how a wiki app mounts five of them.

expected.graph.json

A way in registered once, over a collection — which is how a repository mounts a plugin's routes when the plugins are loaded from disk at start-up.

expected.graph.json

One directory that is honestly both halves: a Koa server under src/server, a React screen under src/web, and one package.json declaring both.

expected.graph.json

One Koa service, read by the same table row as Express and Fastify.

expected.graph.json

A repository whose routes are declared by where its files are, read by the reading every file-system router in this tool shares — Medusa v2 in miniature.

expected.graph.json

One repository whose server actions are written the way the ecosystem actually writes them: built by a helper rather than declared as functions.

expected.link-report.json expected.project-graph.json

Three applications in one service, a request written inside each of them, and one written outside all three.

expected.link-report.json expected.project-graph.json

Two repositories, and both of them are here for the same failure: the tool reporting a clean bill of health on something it did not read.

expected.contracts-report.json expected.doctor.shop.txt expected.doctor.txt expected.link-report.json expected.project-graph.json

One service whose code is in two directories, which is what R96 turned out to be about.

expected.link-report.json expected.project-graph.json

One repository, two whole applications, and the same address declared in both.

expected.graph.json

Three ways in, and not one of them is written in the file that serves it.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A Next.js application that imports a DTO package built for a Nest API, and is not itself a Nest application (R143).

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A tRPC server whose procedures reach the database through ctx, with nothing annotated and nothing installed: no @trpc/server, no generated @prisma/client.

expected.graph.json

The other half of fixtures/trpc-router: callers of procedures, joined to the procedures they reach.

expected.link-report.json expected.project-graph.json

A repository whose ways in are not routes, which is what R95 turned out to be about.

expected.graph.json

One repository, one segment, and two ends that have to agree about it.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

One browser, three client classes it wrote itself, and the question R87 asked: what happens when the thing that makes a request is not a package.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

Two repositories that ship as one product, and the pair exists to prove one sentence: a click in a React component reaches a route a Next.js file-system router answers, and the tool can say so from a different checkout.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A browser repository with no tsconfig in it, which is the shape extract meets whenever it is pointed at a bare directory rather than at a configured project.

expected.graph.json

A React Router v7 repository whose routes are declared in app/routes.ts rather than spelled by file names (P43).

expected.graph.json

One Angular repository, holding each construct the extractor has a rule for exactly once: a standalone component and two a module declares, three more a route loads rather than names, every kind of trigger a template can carry, injection through a constructor and through a field, five requests covering every way an address can be read, and the two annotations.

expected.contracts-report.json expected.graph.json expected.link-report.json expected.project-graph.json

One Angular repository whose requests are all written inside shared wrappers, so that no request can be read where the network is reached.

expected.contracts-report.json expected.graph.json expected.link-report.json expected.project-graph.json

The shapes a real Angular route configuration is written in, none of which is a const routes: Routes passed straight to the router.

expected.graph.json

One Angular repository and one Nest repository, for the single question of what a service's base address is allowed to look like.

expected.link-report.json expected.project-graph.json

A bot whose buttons are functions in a table it keeps itself, and whose commands are registered inside module-level functions.

expected.contracts-report.json expected.graph.json expected.link-report.json expected.project-graph.json

What the reader could not follow, grouped by cause (P75).

expected.cli expected.link-report.json expected.mcp expected.project-graph.json

One repository built on a framework this tool has never heard of, read entirely from a description in flowatlas.config.json.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

An Express service for a lending library whose every data access goes through @acme/data-kit, a shared package the repository declares and nobody installed.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A bookshop of three services whose wrappers are its own and come from packages nobody here installed (P121): catalog publishes through ShopBus.emit({ topic, data }) and calls stock through ApiClient.call('POST', url, body), stock handles through ShopBus.on('book.added', handler), and the React storefront requests through useApi().send({ method, path }).

expected.cli expected.contracts-report.json expected.link-report.json expected.mcp expected.project-graph.json

Exercises P89: one query-in-loop row per loop, loops bounded on purpose set aside and counted, per-item loops as notes, and the rest ranked by how many ways in reach them.

expected.cli expected.contracts-report.json expected.link-report.json expected.mcp expected.project-graph.json

The repository nobody added to the configuration (P122).

expected.cli expected.contracts-report.json expected.link-report.json expected.mcp expected.mcp.traffic expected.project-graph.json

A repository whose routes are Remix flat routes, read by the reading every file-system router in this tool shares (P38).

expected.graph.json

What a request carries and what it is answered with, read from four frameworks whose handlers do not say so in their signature, and compared with an Angular client that calls two of them.

expected.contracts-report.json expected.link-report.json expected.project-graph.json

A hand-written sample of the graph schema itself, not a repository: no manifest, no configuration, no sources, nothing for the tool to run over.

expected.graph.json

A lending library's returns service whose code names a queue, a topic and a bus by a variable of its environment with a default beside it: process.env.RETURNS_QUEUE_URL ?? '<url>', ?? ITEM_RETURNED_TOPIC and process.env.EVENT_BUS_NAME || 'library-events' (R175).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A repository whose routes are SvelteKit's +server.ts files and page server modules (P42), read by the reading every file-system router in this tool shares (P38).

expected.graph.json

Tables written down one step away from the query, read without configuration (P88).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

What stands in for a package that is not installed (P78).

expected.cli expected.contracts-report.json expected.link-report.json expected.project-graph.json

A repository of four files, one of which is not TypeScript at all.

expected.graph.json