minimal.dev valid

minimal.dev

Minimal is a declarative isolation runtime for Claude Code, Gemini, Codex, Pi, and more: run multiple agents safely on your stack, powered by a verified software supply chain.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T09:46:38.855Z. Cached copy · Source on minimal.dev

# minimal.dev

> Minimal is a declarative isolation runtime for Claude Code, Gemini, Codex, Pi, and more: run multiple agents safely on your stack, powered by a verified software supply chain.

The package catalog tracks the gominimal/pkgs repository. Every catalog
surface is anchored at a commit sha of that repo — either floating with the
latest commit or pinned to a specific sha (content-addressed).

The sha-pinned JSON endpoints require a signed-in session: they answer 401
without one, and both the 401 and the signed-in payload are private/no-store.
The MCP server has no way to present a session, so passing a sha to an MCP
tool returns an error result. The floating-latest surfaces below stay
anonymous.

## Pages

- [Home](https://minimal.dev/): product overview of Minimal's hermetic build environments
- [Whitepaper](https://minimal.dev/blog/whitepaper): why and how hermetic, reproducible environments work
- [Company](https://minimal.dev/company): team and open roles
- [Packages](https://minimal.dev/pkgs): the packages landing — a spotlighted package, a rotating selection of featured ones, and recent writing on software supply chain security
- [Package search](https://minimal.dev/pkgs/search): browsable catalog of Minimal's curated, hermetically-built packages — search, filter and sort by versions, advisories, dependencies, scorecards
- [Package scores](https://minimal.dev/docs/reference/scorecard): what the OpenSSF Scorecard figure on a package page is — the 0-10 aggregate and raw per-check scores, from OpenSSF's weekly scan or, where OpenSSF does not cover the repository, from Minimal running the Scorecard tool — why some packages have none, and how a maintainer can raise each check or get scanned by OpenSSF
- [Documentation](https://minimal.dev/docs): guides and reference for Minimal — getting started, the dev shell, agent shell, building, and tasks; every page is listed under Documentation below
- [Blog](https://minimal.dev/blog): release recaps and writing on hermetic builds, sessions, and software supply chain security; every post is listed under Blog posts below
- [Changelog](https://minimal.dev/changelog): dated release notes — what shipped, newest first
- [Advisories](https://minimal.dev/pkgs/advisories): every security advisory affecting the package catalog, filterable by severity and status; floats with the latest commit
- [Catalog changes](https://minimal.dev/pkgs/changes): what moved between catalog commits — packages added or removed, version bumps, advisory-count shifts; floats with the latest commit

## Full text

- [/llms-full.txt](https://minimal.dev/llms-full.txt): every documentation page, blog post and changelog entry concatenated into one markdown document, each section naming the page it mirrors

## Documentation

- [Getting started](https://minimal.dev/docs/start/1-getting-started): Quickstart for Minimal: install the CLI, initialize a project, and define your toolchain and dependencies for local-first, sandboxed builds.
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=minimal.dev · GET /v1/domain/minimal.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for minimal.dev:
1. POST https://agentwebmap.com/v1/sites/minimal.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://minimal.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/minimal.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/minimal.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.