1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
[]
= "git-xcrypt"
= "0.1.1"
= "2024"
# Measured, not guessed. Edition 2024 alone needs 1.85, but the code uses `let`
# chains in `if` conditions, which are stable only from 1.88 — on 1.85 the crate
# does not compile at all (12 × E0658). The whole suite passes on 1.88, so that
# is the floor, and the `msrv` job in CI holds it there: a bump has to be a
# decision, not a side effect of an edit nobody noticed.
= "1.88"
= "MIT OR Apache-2.0"
= "Transparent, deterministic encryption of selected files in a git repository: plaintext in your working tree, ciphertext in the remote."
= "https://github.com/rkarpin1/git-xcrypt"
= "https://github.com/rkarpin1/git-xcrypt"
= "https://docs.rs/git-xcrypt"
= "README.md"
= ["git", "encryption", "secrets", "aes-siv", "cli"]
= ["command-line-utilities", "cryptography", "development-tools"]
= ["/context", "/.idea", "/.github"]
[]
# AGENTS.md makes "zero unsafe" a hard rule; this is what enforces it.
= "forbid"
[]
# A pre-release, deliberately, and it buys one thing: `aes-siv` 0.8 pulls `aes`
# 0.9, which compiles the aarch64 backend unconditionally and picks it at
# *runtime* through `cpufeatures` — no opt-in cfg. That is what lets
# `.cargo/config.toml` go away, and with it the gap where `cargo install
# git-xcrypt` from a registry ran the software backend on Apple Silicon while a
# build from a clone did not.
#
# The risk is narrower than "rc" suggests, measured rather than assumed: the
# only pre-release package in the whole graph is this one — `aead` 0.6.1,
# `cipher` 0.5.2, `digest` 0.11.3, `cmac` 0.8.0, `ctr` 0.10.1, `dbl` 0.5.0 and
# `aes` 0.9.2 all resolve to stable, and every one of them declares MSRV 1.85,
# so the 1.88 floor is untouched. The requirement lifts itself to 0.8.0 when
# that lands.
#
# Not one stored byte moves: all four frozen vectors in
# `tests/format_vectors.rs` reproduce byte for byte under 0.8, decrypt back, and
# RFC 5297 A.1 still matches. RFC 5297 is frozen, so the crate version cannot
# enter the format — but that is the argument, and the vectors are the proof.
= "0.8.0-rc.3"
= "0.23"
= "1.13.0"
= { = "4.6.5", = ["derive"] }
= "0.4.3"
# `status` has to answer "would git run our filter for this path" the way
# `git check-attr` answers it — nested `.gitattributes`, `info/attributes`,
# `[attr]` macros, last match wins. Naming suspicious lines instead was the last
# route to a green report on a repository that stores plaintext. Measured before
# adding it: `cargo add` locks exactly one package, because everything this
# crate needs is already in the graph through `gix-config` and `gix-glob`.
= "0.34.0"
= "0.59.0"
= { = "0.54.0", = ["sha1"] }
= "0.27.0"
= { = "0.26", = ["sha1", "sha256"] }
# The history scan needs to read the object database itself: `status` has to
# answer whether a declared path ever sat in a commit in the clear, and no
# amount of working-tree inspection can. Both hash kinds, because `gitindex`
# already handles SHA-256 repositories and a scan that quietly skipped them
# would be the wrong kind of silence.
= { = "0.63.0", = ["sha1", "sha256"] }
= { = "0.83.0", = ["sha1", "sha256"] }
= "0.12.4"
= { = "0.66.0", = ["sha1", "sha256"] }
= "0.13.0"
= "0.11.0"
= "2.0.19"
= { = "1.9.0", = ["derive"] }
[]
= "1.11.0"
= "3.27.0"
# A shipped binary is what FR-011 promises, so the release profile is part of
# the product rather than a preference. `panic = "abort"` is deliberately *not*
# set: `lock` and `unlock` walk a working tree file by file, and an abort there
# would skip the reporting that tells a user which files were already rewritten.
[]
= 3
= "thin"
= 1
= "symbols"