<commit_before>page_title: TarSum checksum specification
page_description: Documentation for algorithms used in the TarSum checksum calculation
page_keywords: docker, checksum, validation, tarsum

# TarSum Checksum Specification

## Abstract

This document describes the algorithms used in performing the TarSum checksum
calculation on filesystem layers, the need for this method over existing
methods, and the versioning of this calculation.


## Introduction

The transportation of filesystems, regarding Docker, is done with tar(1)
archives. There are a variety of tar serialization formats [2], and a key<commit_msg>tarsum: add a big fat warning<commit_after>page_title: TarSum checksum specification
page_description: Documentation for algorithms used in the TarSum checksum calculation
page_keywords: docker, checksum, validation, tarsum

# TarSum Checksum Specification

## Abstract

This document describes the algorithms used in performing the TarSum checksum
calculation on filesystem layers, the need for this method over existing
methods, and the versioning of this calculation.

## Warning

This checksum algorithm is for best-effort comparison of file trees with fuzzy logic.

This is _not_ a cryptographic attestation, and should not be considered secure.

## Introduction

The transportation of filesystems, regarding Docker, is done with tar(1)
archives. There are a variety of tar serialization formats [2], and a key
{'fraction_non_alphanumeric': 0.0397212543554007, 'fraction_numerical': 0.0027874564459930314, 'mean_word_length': 5.838095238095238, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '208189', 'n_tokens_mistral': 358, 'n_tokens_neox': 340, 'n_words': 182}