# checksum_repository_agent **Repository Path**: 121786404/checksum_repository_agent ## Basic Information - **Project Name**: checksum_repository_agent - **Description**: https://github.com/triton-inference-server/checksum_repository_agent - **Primary Language**: Unknown - **License**: BSD-3-Clause - **Default Branch**: r25.06 - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2025-07-14 - **Last Updated**: 2026-01-13 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README [![License](https://img.shields.io/badge/License-BSD3-lightgrey.svg)](https://opensource.org/licenses/BSD-3-Clause) # Triton Checksum Repository Agent This repo contains an example [repository agent](https://github.com/triton-inference-server/server/blob/master/docs/repository_agents.md) for verifying file checksums before loading the model. Ask questions or report problems in the main Triton [issues page](https://github.com/triton-inference-server/server/issues). ## Build the Checksum Repository Agent Use a recent cmake to build. First install the required dependencies. ``` $ apt-get install openssl-dev ``` To build the repository agent: ``` $ mkdir build $ cd build $ cmake -DCMAKE_INSTALL_PREFIX:PATH=`pwd`/install .. $ make install ``` The following required Triton repositories will be pulled and used in the build. By default the "main" branch/tag will be used for each repo but the following CMake arguments can be used to override. * triton-inference-server/core: -DTRITON_CORE_REPO_TAG=[tag] * triton-inference-server/common: -DTRITON_COMMON_REPO_TAG=[tag] ## Using the Checksum Repository Agent The checksum repository agent is configured by specifying expected checksum values in the [*ModelRepositoryAgents* section of the model configuration](https://github.com/triton-inference-server/common/blob/main/protobuf/model_config.proto). A separate parameter is used for each file checksum in the following way: the key specifies the message digest algorithm that is used to generate the checksum and the path to file relative to the model repository as \ and the value specifies the expected checksum of the file. Currently the checksum repository agent only supports MD5 checksums. For example: ``` model_repository_agents { agents [ { name: "checksum", parameters { key: "MD5:embedding_table", value: "d726e132f91f16ebee703d96f6f73cb1" } } ] } ``` With the above configuration, the checksum repository agent will be invoked before loading the model and loading will fail if the MD5 checksum for file "embedding_table" does not match the specified value.