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
<!-- Copyright (c) 2018-2026 [Ribose Inc](https://www.ribose.com). -->
<!--
// Redistribution and use in source and binary forms, with or without
// modification, are permitted provided that the following conditions
// are met:
// 1. Redistributions of source code must retain the above copyright
// notice, this list of conditions and the following disclaimer.
// 2. Redistributions in binary form must reproduce the above copyright
// notice, this list of conditions and the following disclaimer in the
// documentation and/or other materials provided with the distribution.
//
// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
// ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-->
# Software Bill of Materials
`enprot sbom` emits an SBOM **for the enprot binary itself** — distinct
from `enprot manifest`, which describes the *content* enprot protects.
```sh
enprot sbom # SPDX 2.3 JSON to stdout
enprot sbom --sbom-format cyclonedx-json --output enprot.cdx.json
```
## What it lists
| Source | How obtained |
|---|---|
| enprot itself | build version |
| Every Rust crate in the build | baked in from `Cargo.lock` at build time (build.rs) |
| Botan | the linked library's own version API, at runtime |
| librnp | the linked library's own version API, at runtime |
Because the C-library versions are queried from the linked libraries,
an SBOM generated by *running* a released binary reports **that
binary's** actual C dependencies — not build-environment assumptions.
## Determinism
- The SPDX `documentNamespace` and the CycloneDX `serialNumber`
derive from a SHA3-256 fingerprint of the component list: the same
inputs always produce the same identifiers.
- The creation timestamp honors `SOURCE_DATE_EPOCH` when set (the
release pipeline sets it to the tag's commit timestamp), so
identical releases produce byte-identical SBOMs. See
[reproducible-builds.md](reproducible-builds.md).
- Packages use SPDX `NOASSERTION` licenses: `Cargo.lock` carries no
per-crate license metadata, and the SBOM does not guess.
## Release artifacts
Every release ships `enprot-<version>.spdx.json` and
`enprot-<version>.cdx.json` alongside the binaries, generated by the
binary that was just built. Both feed standard tooling
(`grype enprot-<version>.spdx.json`, Trivy, compliance platforms).