This release is a pre-release and may not be stable for production use.
PriorFolio
Prepare IP disclosures and preserve the evidence behind them.
Alpha release: CI exercises the desktop and command-line workflows on Windows, Linux, and macOS with Python 3.10, 3.12, and 3.15.
PriorFolio records local projects, lets you describe the work and your contribution, and produces a disclosure plus private evidence. It hashes the actual files on disk, including uncommitted edits. It never commits, stages, fetches, or writes inside the projects being scanned.
Run
Requires Python 3.10+ and Git. The desktop interface also requires Tkinter (included with the standard Windows Python installer; some Linux installations need their distribution's Tk package). Runtime code uses the Python standard library. Windows is also exercised locally using real Tk windows.
From a source checkout, install in a virtual environment and launch:
python -m pip install .
priorfolio --gui
priorfolio --help
python gui.py also works directly from a checkout. The installed desktop
launcher is priorfolio-gui; python -m priorfolio --gui is an alternative.
Install the pinned alpha release from PyPI:
python -m pip install "priorfolio==0.1.0a2"
priorfolio --gui
Git must be installed separately and available on PATH. Tkinter is needed
only for the desktop interface; pip cannot install the system Tk libraries.
Desktop downloads and builds
The Desktop builds workflow creates Windows x64, Linux x64 and macOS arm64 archives with a windowed PriorFolio app and a separate PriorFolioCLI. Python and Tk are bundled; Git is still installed separately. Download an archive from GitHub releases, extract it completely and keep each application folder intact. Initial builds are unsigned and macOS builds are not notarized.
To build locally on the operating system you intend to distribute for:
python -m pip install -e ".[desktop]"
python scripts/build_desktop.py
The build checks GUI startup without opening a visible window and exercises
generation, snapshots, backup export and restoration through the frozen CLI.
Archives and SHA-256 sidecars go to dist/desktop/. Linux builds use Ubuntu 22.04;
macOS and Linux archives preserve the bundle's symlinks and executable permissions.
Runtime license notices are included. The Tcl/Tk fallback notices come from the
official Tcl and
Tk 8.6 distributions.
Disclosure workflow
- Add a folder of projects, or Add single project for an individual folder.
- Focus a project row and select Project details. Enter a public title, description, your contribution, dates or period of work, and references.
- Tick the projects to include. Space toggles the focused row. Keep Zip snapshots enabled to preserve the actual source bytes.
- Generate, then review the Disclosure tab before sharing
disclosure.zip. - Export backup to create the complete private ZIP. Email it to yourself using the Backup email text, or save it to a private cloud-sync folder.
- Check the received email attachment or the completed upload through the
provider's web interface, ideally from another device. Compare the downloaded
ZIP's SHA-256 with its
.sha256sidecar, then Confirm remote backup.
Saving a local ZIP is not a completed remote backup. PriorFolio distinguishes backup required, exported, and confirmed by you. It does not send email, upload files, or independently verify delivery. An email containing only a hash does not back up the underlying source files. If the ZIP exceeds your mail provider's attachment limit, use private cloud storage.
The desktop app remembers the latest run and its pending backup when reopened, and remembers earlier runs through Previous runs. Confirming a newer backup does not clear reminders for older unconfirmed runs. The app checks all saved runs before closing.
Generated document previews are read-only and match the saved exports. Edit Project details and generate a new run to change a disclosure. Opening another run switches the documents and backup actions together.
Runs default to ~/PriorFolio/runs/. GUI sources and disclosure details are
stored privately in ~/.priorfolio/settings.json. There is no telemetry.
What can be shared?
| Output | Contents and intended use |
|---|---|
disclosure.md, disclosure.json, disclosure.zip |
Project titles, descriptions, contributions, supplied dates/references, commit identifiers, content hashes and counts. Review before sharing. |
evidence.json, evidence.md, manifests/ |
Private local paths, remote identifiers, source file names, hashes and warnings. |
snapshots/ |
Private ZIPs containing the exact source bytes hashed. |
evidence_bundle.zip |
Private metadata only, without snapshots. Not a complete source backup. |
| Exported backup ZIP | Private complete evidence, including snapshots, metadata, disclosure documents, and timestamp responses if requested. |
email.txt, BACKUP.txt |
Email-to-yourself template and backup/restore instructions. |
backup_status.json |
Local export receipt and your remote-copy confirmation; excluded from disclosures and exported backups. |
Disclosure exports omit automatic local paths, remote URLs, file listings, and source contents. Anything you type into the disclosure fields is shared as entered. The private backup is not encrypted and may contain credentials from the selected projects. Use storage you control with suitable access restrictions. PriorFolio deliberately preserves exact evidence rather than silently removing source files.
Command line
priorfolio --root D:\projects --list
priorfolio --add D:\projects\example --select all
priorfolio --root D:\projects --select "1,4-7,example-project" --out D:\records
priorfolio --backup RUN_FOLDER --destination D:\CloudSync\PriorFolio-private.zip
priorfolio --confirm-backup RUN_FOLDER --backup-method cloud
Snapshots are on by default. --no-snapshot creates a hash-only record that
cannot provide a complete source backup. --add alone scans only the supplied
projects. With no roots or individual projects, the CLI scans the current folder.
Disclosure details can currently be authored through the GUI.
Verify and restore
Unpack your own complete backup ZIP into an empty directory, then:
priorfolio --verify RESTORED_FOLDER --expect RECORDED_BUNDLE_SHA256
priorfolio --verify RESTORED_FOLDER --expect RECORDED_BUNDLE_SHA256 --against-disk
priorfolio --verify UNPACKED_METADATA_BUNDLE --metadata-only --expect RECORDED_BUNDLE_SHA256
Full verification requires every recorded snapshot. Metadata only explicitly
skips snapshot checking; it never certifies a complete backup. The GUI exposes
the same option. Project paths are read only when Compare local projects or
--against-disk is enabled. Enable that only on a run you created or trust.
Comparisons report changed/missing files, not newly added files.
The bundle hash is SHA-256 of evidence.json; keep it separately, such as in
your email. A folder containing its own hashes only proves self-consistency.
An independently retained expected hash ties verification to your earlier record.
The backup ZIP's sidecar hash is a separate checksum of the entire exported ZIP.
The content hash is SHA-256 of a UTF-8 manifest, sorted by relative path, with
one SHA-256 per file. Manifests follow sha256sum -c escaping conventions.
Line-ending conversions or Unicode filename normalization can change the bytes
on a new checkout. Keep the snapshots to reproduce the recorded state exactly.
Timestamp responses
Timestamp requests are off by default. --timestamp or Request timestamps
sends the evidence JSON's SHA-256 and a random nonce to DigiCert, Sectigo and
FreeTSA. No project names or source bytes are sent. The services receive the
request's network metadata, including the originating IP address.
PriorFolio stores the responses and checks basic status/digest consistency. It does not validate timestamp signatures or certificate trust. Reported times are unverified labels, and a successful hash check is not proof of an authentic timestamp. Two configured endpoints use HTTP; responses must not be trusted without independent signature verification.
For external verification with an independently trusted TSA certificate bundle:
openssl ts -reply -in timestamps/digicert.tsr -text
openssl ts -verify -data evidence.json -in timestamps/digicert.tsr -CAfile trusted-tsa-ca-bundle.pem
Scope and limits
- Hashes identify bytes; they do not establish authorship, ownership or a date. Git commit dates and user-entered dates are recorded claims.
- Git-tracked files and untracked, non-ignored files are included. Dependency folders, caches and virtual environments are skipped when untracked.
- Symlinks, junctions, nested repositories and submodules are not followed. Add nested repositories separately. Every intentional exclusion is noted.
- Read failures produce warnings. Review them; a verified incomplete record remains incomplete. This is a sequential snapshot, not an atomic filesystem freeze.
- PriorFolio is not legal advice. Review disclosure wording for your situation.
Development and license
python -m pip install -e ".[dev]"
python -m pytest
python -m pytest --cov --cov-report=term-missing --cov-report=json:coverage.json
python -m build
python -m twine check --strict dist/*
python scripts/check_dist.py dist
Tests create synthetic projects in temporary directories. GUI tests exercise
real Tk windows and skip when a display is unavailable. Set
PRIORFOLIO_TEST_OFFSCREEN=1 to keep test windows outside the visible desktop;
this still requires a working display. PRIORFOLIO_NETWORK=1
enables live timestamp-service tests; PRIORFOLIO_SLOW=1 enables a 2.2 GB fixture.
The coverage badge reports measured line coverage of the CLI, export logic and
GUI, including subprocess execution. CI also records branch coverage. Build and
launcher scripts are outside that application metric. The badge updates after
the full test matrix passes on main; PyPI's version badge resolves after the
first package upload.
See Contributing,
Security, and
Releasing.
Copyright (c) 2026 Jesse Anderson. Licensed under the GNU General Public License, version 3 only (GPL-3.0-only); see LICENSE. Provided without warranty. The application license does not change the license of your inputs.
Metadata
Release files for priorfolio 0.1.0a2
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 |
|---|---|---|---|---|
| priorfolio-0.1.0a2.tar.gz | 139.8 kB | With provenance | Details for priorfolio-0.1.0a2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| priorfolio-0.1.0a2-py3-none-any.whl | Python 3 | none | any | Details for priorfolio-0.1.0a2-py3-none-any.whl |
Total release size: 192.4 kB
Release files / priorfolio-0.1.0a2.tar.gz
| Download URL | priorfolio-0.1.0a2.tar.gz |
|---|---|
| Size | 139.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46c4303782462ff31ce021048c1ee924dd6935e59ef76b6d078264b251b8d599
|
|
BLAKE2b-256 checksum How to use checksums |
59135a4b7ec0be37f95cdf4799924d7ed2af99bbba3c56404c7c9706805c1aea
|
| 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 Nov 8, 2026.
Transparency logRelease files / priorfolio-0.1.0a2-py3-none-any.whl
| Download URL | priorfolio-0.1.0a2-py3-none-any.whl |
|---|---|
| Size | 52.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
153506331bc7f28896245212bb849b0cb9572b417dd6f906163ea6aa83599bec
|
|
BLAKE2b-256 checksum How to use checksums |
94395858d89b121e34e9e274761254d1d74e954a2b0f4f8beb77c1857781fb57
|
| 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 Nov 8, 2026.
Transparency logSecurity for priorfolio 0.1.0a2
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
Both files in this release have been uploaded with provenance metadata.
Attestation for priorfolio-0.1.0a2.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 Nov 8, 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.