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

# ENS Text Records

> Package metadata stored on ENS for decentralized discovery.

# ENS Text Records

When you publish via `opm push`, package metadata is written to your ENS name as text records — creating a decentralized discovery layer independent of the smart contract.

## Record Keys

### Author-Level (on `djpai.eth`)

| Key | Example |
| - | - |
| `opm.version` | `1.2.3` |
| `opm.checksum` | `0x8a3f...` |
| `opm.fileverse` | Fileverse report URI |
| `opm.risk_score` | `12` |
| `opm.signature` | ECDSA signature |
| `opm.contract` | Registry contract address |
| `opm.packages` | `express,lodash` |

### Per-Package (namespaced)

`opm.pkg.<name>.version`, `opm.pkg.<name>.checksum`, `opm.pkg.<name>.fileverse`, etc.

## Subnames

OPM creates ENS subnames like `express.djpai.eth` during `opm push` if you own the parent name. Each subname gets its own text records for per-package resolution.

## Contenthash

The ENS `contenthash` is set to the Fileverse IPFS CID — read directly from the Fileverse Portal smart contract. This makes audit reports discoverable via standard ENS contenthash resolution.

## When Records Are Used

* **`opm push`** — Writes all records after on-chain registration
* **`opm info`** / **`opm view`** — Reads and displays records alongside on-chain data
* **`opm install express@djpai.eth`** — Resolves the ENS author, reads metadata

> [!NOTE]
>
> Writing records requires the signer (`OPM_SIGNING_KEY`) to own/manage the ENS name. Reading is permissionless.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.