CopyOfA
CopyOfA is a preservation and forensic toolkit for music collectors. It acquires and maintains trustworthy evidence of recorded audio, then lets collectors analyze, compare, and share what that evidence reveals.
Status
The project is restarting from a clean slate. Its first release, v0.1.0, preserves a selected file delivery as an Evidence Set and verifies it later. The roadmap in the Product Map lists what comes next.
The previous implementation, which archived optical discs bit-exactly with redumper, is
retired. Its last code change is commit 0d04a38 in the Git history. It does not define
the new architecture or release sequence.
Installation
CopyOfA runs on macOS and Linux with Python 3.11 or later. Install it from PyPI with uv:
uv tool install copyofa
Usage
Preserve files you already own, such as a download purchase, as a new Evidence Set:
copyofa import ~/Downloads/Album --to /Volumes/Archive/Album \
--note "Bandcamp purchase" --ref discogs=r123456
- Each source, a file or a directory, goes into the set under its base name.
--tonames a directory that must not exist yet; the set appears there only once every stored copy has been checked against its source.--exclude <pattern>leaves out files and directories by shell-style pattern; operating system metadata files such as.DS_Store, symbolic links, and empty directories are left out too. Every exclusion is recorded with its reason.--noteand--refrecord provenance exactly as given;--refrepeats.--jsonprints the result as JSON. Progress and errors go to stderr.
The command exits 0 when the set is accepted, 1 when the import is refused or fails, 2 for invalid arguments, and 130 when canceled with Ctrl-C. Evidence Set format describes the set and how to check it without CopyOfA.
Later, after moving the set or just to check it, verify it against its Integrity Baseline:
copyofa verify /Volumes/Archive/Album
copyofa verify /Volumes/Archive/Album --json > album-verification.json
Verify reads every preserved file and reports each one as matching, changed, missing,
unavailable, or not checked, and lists unexpected files under data/. Operating
system metadata files that Finder adds while browsing the set are ignored. It writes
nothing into the set. --json prints a verification Report, which
Verification Report format describes.
Verify exits 0 when everything is intact, 1 when it found anything else, 2 when the target is not an Evidence Set or the arguments are invalid, and 130 when canceled.
Documents
- Manifesto: vision, target users, principles and non-goals.
- Product Map: capabilities, collector scenarios, core concepts, and the Now / Next / Later roadmap.
- Briefs: the scope and acceptance criteria of planned work.
- Decisions: architecture decision records.
- Formats: the files CopyOfA writes.
GitHub release milestones and their issues will hold the committed work.
Development
just setup # Install dependencies and git hooks
just qa # Run all checks
just test # Run the tests
CONTRIBUTING.md covers the development setup, pull requests and releases; AGENTS.md holds the commands and conventions for contributors and coding agents.
License
CopyOfA is licensed under the Apache License 2.0.
Metadata
Release files for copyofa 0.1.0
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 |
|---|---|---|---|---|
| copyofa-0.1.0.tar.gz | 19.2 kB | With provenance | Details for copyofa-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| copyofa-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for copyofa-0.1.0-py3-none-any.whl |
Total release size: 40.3 kB
Release files / copyofa-0.1.0.tar.gz
| Download URL | copyofa-0.1.0.tar.gz |
|---|---|
| Size | 19.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3332236d1891624e4ae0d7b3457ce49425febf11da7fa65c5f43bc497b6a3db7
|
|
BLAKE2b-256 checksum How to use checksums |
46be0e721ad5e02d577a2d269e35d3d5f75859532bca2b66a691d91345c29e1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logRelease files / copyofa-0.1.0-py3-none-any.whl
| Download URL | copyofa-0.1.0-py3-none-any.whl |
|---|---|
| Size | 21.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d3dfe1fce9a7051afc91bde772a3b099a0ee17ad151f698d616dc7e08fb4da75
|
|
BLAKE2b-256 checksum How to use checksums |
52aeee164f4dbdc9e9b4a9ed3467bd9c6b57cbeb86ef4442d77679cecbe601a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logSecurity for copyofa 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for copyofa-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logA 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.