The Update Framework
theupdateframework.io
- Free plan
What The Update Framework is
The Update Framework (TUF) is an open-source framework and specification for securing software update systems. Developers can integrate it with application updaters, language package managers, operating-system package managers, and other systems distributing packages or digital artifacts. TUF uses signed metadata to identify trusted files, downloads them, and verifies them before handing them to the update system. The update system applies files; TUF does not define package formats or perform that installation. Its design addresses rollback, freeze, fast-forward, endless-data, mix-and-match, wrong-file, malicious-mirror, and key-compromise attacks. Multiple signing keys, signature thresholds, key revocation and replacement, and reduced reliance on online keys help manage trust. Reference implementations are available in Python, Go, JavaScript, and Rust, with third-party implementations in PHP and AWS Labs’ Tough. Related projects include Repository Service for TUF, tuf-on-ci, Uptane, The Archive Framework, and TUF Browser. TUF is intended to integrate with new or existing content-delivery and update systems. It is free, and the project is managed by the Linux Foundation under the Cloud Native Computing Foundation.
Who it suits
TUF suits developers and organizations building or securing software update, package-management, and artifact-distribution systems. It is relevant where repository or signing-key compromise must be considered.
Good to know, and what to watch
- Protects against multiple update-system attack types
- Supports key thresholds, revocation, and replacement
- Reference implementations span four programming languages
- Integrates with existing delivery and update systems
- Open source and free to adopt
- Does not define package formats
- Does not apply application-file updates
- Does not bootstrap secure installation of arbitrary new software
The verdict
TUF adds signed-metadata verification and flexible key controls to software update systems. Teams must supply the package format and installation machinery around the framework.
What the maker publishes
- Browser implementation
- The official site describes TUF Browser as a minimal TypeScript implementation intended to be compatible with browsers. source
- Community support
- The project directs questions and feedback to its Google group and CNCF Slack channel, and lists community meetings as a way to participate. source
- Docker adoption
- The official adoptions page lists Docker registry bindings and a Rust implementation. source
- Founded
- 2009 source
- Governance
- The project’s about page says TUF is managed by the Linux Foundation under the Cloud Native Computing Foundation. source
- How it works
- TUF uses signed metadata to identify trusted update files, downloads them, and checks them before handing them to the software update system. source
- Implementations
- The project lists reference implementations in Python, Go, JavaScript, and Rust, plus third-party implementations in PHP and AWS Labs’ Tough. source
- Integration
- TUF is intended to integrate with new and existing content delivery systems and software update systems. source
- Integrations
- The official getting-started page lists python-tuf, go-tuf, tuf-js, and rust-tuf as reference implementations, and php-tuf and AWS Labs’ tough as third-party implementations. source
- Intended users
- The framework is intended for software update systems such as application updaters, programming language library package managers, and operating system package managers. source
- Key controls
- TUF supports multiple keys, signature thresholds, key replacement and revocation, and reduced trust in keys used online or automatically. source
- Key resilience
- TUF supports multiple signing keys and signature thresholds, revocation and replacement of keys, and minimizing trust in keys kept online. source
- Limit
- TUF does not define package formats or perform the actual update of application files. source
- Limitations
- TUF does not define a universal update system or package formats, perform the actual application file update, or bootstrap secure installation of arbitrary new software. source
- Project history
- The project history page says the basic technology was developed at the University of Washington in 2009 and that TUF has been based at NYU Tandon since 2011. source
- Project status
- The project website describes TUF as open source and a graduated CNCF project. source
- Project status
- TUF is a graduated CNCF project. source
- Protection
- TUF is designed to protect update systems even when an attacker compromises a repository or signing keys. source
- Purpose
- TUF is a framework and specification developers can adopt to secure new and existing software update systems. source
- Purpose
- TUF is a framework for securing new and existing software update systems, designed to protect against repository and signing key compromise. source
- Related systems
- Listed systems include Repository Service for TUF, tuf-on-ci, Uptane, The Archive Framework, and TUF Browser. source
- Security audits
- The official security audits page lists public reports dated 2015, 2017, 2018, 2022, and 2024, covering TUF and several related implementations or projects. source
- Signing systems
- The official site lists Repository Service for TUF for integration with existing artifact repositories, tuf-on-ci for CI and Git forge signing workflows, and Uptane for automotive updates. source
- Support and community
- The specification directs users to the CNCF Slack channel #tuf or the specification repository to report questions and issues. source
Checked against the maker's pages on 8 Oct 2026.