Registry

Source-owned components, dependency resolution, integrity, and secure remote sources.

The registry distributes source files, not opaque runtime widgets. Applications can inspect and customize installed components while sharing package-level contracts.

Install flow

Documentation flow diagram. requested items leads to load and validate manifest; Manifest leads to resolve dependencies; Graph leads to validate file paths and integrity; Files leads to plan every destination; Plan leads to detect conflicts; Conflicts leads to atomic scoped writes — **Documentation flow diagram.** requested items leads to load and validate manifest; Manifest leads to resolve dependencies; Graph leads to validate file paths and integrity; Files leads to plan every destination; Plan leads to detect conflicts; Conflicts leads to atomic scoped writes

Remote sources reject unsupported schemes, credentials in URLs, query or fragment ambiguity, unsafe relative paths, and invalid package or dependency metadata. Plain HTTP is limited to explicit loopback development hosts.

See Custom registries and the @mwillbanks/tuil-registry reference.

Install flow

On this page