pytracer-registry
Layer 5 of pyTracer: turns test collections into shareable, forkable artifacts — the role Postman's collections played for API testing. Collections are versioned (content-addressed history), forkable with lineage, mergeable with conflict detection, access-controlled (private / team / public), and discoverable by framework and use case.
from pytracer_registry import Registry, Visibility, CollectionArtifact
reg = Registry() # in-memory; pass a FilesystemStore for on-disk JSON
col = reg.create_collection(
"alice", CollectionArtifact(name="crewai-rag-tests", framework="crewai"),
visibility=Visibility.PUBLIC,
)
fork = reg.fork("bob", col.id) # independent copy with lineage
reg.commit("bob", fork.id, updated_artifact, "tweak assertions")
pr = reg.open_pull_request("bob", fork.id, col.id, "improve RAG coverage")
reg.merge_pull_request("alice", pr.id) # 3-way merge, raises on conflict
reg.discover(viewer="carol", framework="crewai")
Storage is behind a Store interface (InMemoryStore, FilesystemStore); a
production deployment can back it with a git repo per collection and serve the
same API to a web UI.
1 maintainer
Metadata
1 maintainer
Release files for pytracer-registry 0.1.2
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 | |
|---|---|---|---|---|
| pytracer_registry-0.1.2.tar.gz | 24.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytracer_registry-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 48.4 kB
Release files / pytracer_registry-0.1.2.tar.gz
| Download URL | pytracer_registry-0.1.2.tar.gz |
|---|---|
| Size | 24.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d21acef5f8f0384d4a3fb7bc9ec7c2e682873c5a25f8e7631cf8e6682789ea8
|
|
BLAKE2b-256 checksum How to use checksums |
268662fbd62c6dc3d32552f392bc43951aeb7bc882b5cdac3f5eddc42711ef91
|
| 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 21, 2026.
Transparency logRelease files / pytracer_registry-0.1.2-py3-none-any.whl
| Download URL | pytracer_registry-0.1.2-py3-none-any.whl |
|---|---|
| Size | 24.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8b15e8b2c015c5ec55c49079a0f5d2f1a8cf743ef5a8f0a519a9d7ef6ad6afdc
|
|
BLAKE2b-256 checksum How to use checksums |
de636bf29841273f7b4e218b5db016e531e189095506fb2f66f604958266f615
|
| 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 21, 2026.
Transparency logSecurity for pytracer-registry 0.1.2
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 pytracer_registry-0.1.2.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 21, 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.
