Run Manifest
Run Manifest creator.
Run
Build Manifest Mode
uvx run-manifest "2026-08-13 09:00:00" "2026-08-13 10:00:01" --used-tokens 13 26 54054 832509 7617 --model opus "test/file1.txt" "test/file2.json" "test/file3.md"
--used-tokens is optional and takes 5 numbers, in order: API requests, fresh input, cache creation (written), cache read (replayed context), output. --model is optional and takes the model name. When omitted, the corresponding field is left out of the manifest.
-o/--output is optional and appends the manifest to a JSON array file, creating it if it doesn't exist:
uvx run-manifest "2026-08-13 09:00:00" "2026-08-13 10:00:01" -o manifest.json "test/file1.txt"
After the first run, manifest.json is created with the manifest as the sole element of the root array (never a bare object):
[
{ ... first run's manifest ... }
]
Running the command again appends a second element to that same array:
[
{ ... first run's manifest ... },
{ ... second run's manifest ... }
]
Expected output manifest (1 record):
{
"start": "2026-08-13T06:00:00Z",
"end": "2026-08-13T07:00:01Z",
"runtime": 3601.0,
"model": "opus",
"used-tokens": {
"api-requests": 13,
"input": 26,
"cache-creation": 54054,
"cache-read": 832509,
"output": 7617
},
"input-files": [
{
"name": "test/file1.txt",
"crc32": "c56b525d"
},
{
"name": "test/file2.json",
"crc32": "373d4892"
},
{
"name": "test/file3.md",
"crc32": "98bab5fc"
}
]
}
Check Mode
Verify that a manifest's CRC-32 values still match the files it references:
uvx run-manifest --check manifest.json
manifest.json can be a single manifest object, or a JSON array of manifests such as the one produced by -o/--output above — in that case only the record with the latest end timestamp is checked.
Expected output (one of):
up-to-date
or
outdated: <name of the first file that changed or is missing>
The manifest can also be piped in via stdin instead of a file path:
cat manifest.json | uvx run-manifest --check
Local Run
uvx --from . run-manifest
Metadata
Release files for run-manifest 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| run_manifest-0.1.5.tar.gz | 5.7 kB | Without provenance | Details for run_manifest-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| run_manifest-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for run_manifest-0.1.5-py3-none-any.whl |
Total release size: 11.6 kB
Release files / run_manifest-0.1.5.tar.gz
| Download URL | run_manifest-0.1.5.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ced8854b2d863013cfa28a1c4c013075e193d9f5e21b2e03369c5690bb38396
|
|
BLAKE2b-256 checksum How to use checksums |
2fa66ae542bf3c2fa7034f894a288886a0e86b9497ac6caedc0e89bc3d18ebc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.25 {"installer":{"name":"uv","version":"0.11.25","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / run_manifest-0.1.5-py3-none-any.whl
| Download URL | run_manifest-0.1.5-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
25e769541e5d44a6e9a03a7f528f15d12a2b4821e9af9ac7f537c0c75bb44f97
|
|
BLAKE2b-256 checksum How to use checksums |
98e48d54f1e9e21242cd2c76213accde2660d3e9a19748d46bf6870d1b3dd417
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.25 {"installer":{"name":"uv","version":"0.11.25","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for run-manifest 0.1.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.