Itá Edition 0.4 preview

Capabilities granted · Proofs included

Your dependencies ask.
You grant.

Itá is Una's package manager: a dependency system built so that a library can only do what you grant it, and nothing it ships runs when you fetch it.

Part of the una command from edition 0.4: ita.una describes a package, ita.lock pins it, una ita manages it.

The idea

Dependencies you can read like a contract

Una already checks what a program may do: its capabilities, its contracts, where secrets may flow. Itá carries those checks across package boundaries, so adding a library never widens what your program may do without your say.

Granted, not assumed

A dependency holds no capability unless your package hands it one, within the ceiling you write for it with may. Without a ceiling it reaches no file, no network and no console.

Nothing runs at install

No install scripts, build scripts or hooks: nothing runs when a package is read, checked or built. A dependency's trusted modules need your consent, by name, with trust.

Checked with what the lock pins

ita.lock pins what a package is checked with: the solver, and every package of the program. It is committed with the package.

Locked by content

Every package is pinned in ita.lock with its version, its origin and its content digest. A copy that does not match the lock is refused.

One tool

una ita is part of the una command you already use, not a separate installer: it locks, fetches, updates and audits.

Built for agents too

An agent that adds a dependency gets the same answer a person does: what the library may touch, in plain text, with a diagnostic code for every refusal.

Why it matters

The difference, in one dependency

What happens when a project adds a small library, in a typical ecosystem and in Itá.

A typical package manager

  • The library can read files, open sockets and see environment variables as soon as it is imported.
  • An install script can run arbitrary code on the developer's machine.
  • Its documented behavior is a promise, checked by nobody.
  • A new version can quietly ask for more.

Itá

  • The library uses only the capabilities your package grants it, enforced by the checker.
  • Nothing runs when it is fetched.
  • It is pinned by its content digest, and a copy that differs is refused.
  • A version that asks for more is refused until you accept the wider ceiling, by name.

In this release

What edition 0.4 has

Itá is part of Una from edition 0.4, which is a preview. The pages below are the reference; Known limits says what the preview does not do.

Describe

The manifest and the lock

ita.una names the package, its edition and what it needs. ita.lock pins it, and only the tool writes it.

Depend

Dependencies and their authority

A package needs another by path or from a registry it names, and writes the ceiling of what each may do.

Operate

Commands

una ita locks, fetches, updates and audits. A build reads only the lock, with no network.

itá

Itá means stone in Tupi, the solid thing others build on. Una means dark, or black. Together they name a place in Brazil, Itaúna: the dark stone.

Edition 0.4 is a preview: a later release may change its constructs, commands and file formats before it is declared stable.