> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sqd.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Packages overview

> The Squid SDK packages used in an EVM squid and what each one does.

Squid SDK is modular: a squid combines a chain-specific data source, a store, and optional
code-generation and serving tools. This page lists the packages relevant to EVM
squids.

## One package: `@subsquid/squid-sdk`

For Portal-native EVM squids, the `@subsquid/squid-sdk` package bundles the whole toolkit behind
one dependency with subpath imports:

```ts theme={"system"}
import {run} from '@subsquid/squid-sdk/processor'
import {DataSourceBuilder} from '@subsquid/squid-sdk/evm'
import {TypeormDatabase} from '@subsquid/squid-sdk/store/typeorm'
```

| Subpath                                      | Contents                                                             |
| -------------------------------------------- | -------------------------------------------------------------------- |
| `evm`                                        | EVM Portal stream — [`DataSourceBuilder`](./evm-stream)              |
| `evm/objects`                                | Block augmentation (`augmentBlock`)                                  |
| `evm/rpc`                                    | [RPC data source](./evm-rpc-stream) — needs the optional peers below |
| `evm/fallback`                               | [Fallback data source](./evm-fallback)                               |
| `fallback`                                   | Chain-agnostic fallback machinery (policy types, metrics sink)       |
| `processor`                                  | [`run()` and `Processor`](./batch-processor)                         |
| `store/typeorm`                              | [TypeORM store](./data-stores/typeorm-store)                         |
| `logger`                                     | [Logger](./logger)                                                   |
| `client/portal`, `client/http`, `client/rpc` | Portal, HTTP, and RPC clients                                        |
| `util`, `util/*`                             | Range, hex, JSON, and data-source utilities                          |

Two optional peer packages, `@subsquid/evm-rpc` and `@subsquid/evm-normalization`, are required
only when the `evm/rpc` subpath (or an `rpc` fallback source) is used.

The subpaths also work under the classic TypeScript resolution used by standard squid tsconfigs
(`module: commonjs`) — the package ships per-subpath type redirects, so autocomplete works without
`moduleResolution` changes.

## Individual packages

The same functionality remains available as standalone packages — existing squids need not
migrate:

* [`@subsquid/evm-stream`](./evm-stream) + `@subsquid/batch-processor` — Portal-native data
  source and runner
* `@subsquid/evm-objects` — block augmentation
* [`@subsquid/evm-typegen`](./evm-typegen/generating-utility-modules) — ABI-based utility module
  generator; its output imports `@subsquid/evm-abi` and `@subsquid/evm-codec` (install both)

## Stores

Any store works with any data source:

* [`@subsquid/typeorm-store`](./data-stores/typeorm-store) — PostgreSQL, with
  [`@subsquid/typeorm-codegen`](./typeorm-codegen) (dev dependency) and
  [`@subsquid/typeorm-migration`](./typeorm-migration)
* [`@subsquid/file-store`](./data-stores/file-store) — filesystem datasets (CSV, JSON, Parquet,
  local or S3)
* [`@subsquid/bigquery-store`](./data-stores/bigquery-store) — Google BigQuery

The store contract itself is documented in [Store interface](./data-stores/store-interface).

## Serving and tooling

* [`@subsquid/graphql-server`](./openreader/overview) — the OpenReader GraphQL server, derived
  from the [schema file](./schema-files/schema-files-codegen)
* [Hasura configuration tool](./hasura-configuration) — for Hasura-based APIs
* [`@subsquid/logger`](./logger) — structured logging
* [Squid CLI](/en/cloud/reference/cli/installation) — scaffolding
  ([`sqd init`](./create-squid)), command runner, and SQD Cloud deployment