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.

Metadata

Release files for pytracer-registry 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pytracer-registry 0.1.1
File	Size	Uploaded	Provenance
pytracer_registry-0.1.1.tar.gz	24.1 kB	Oct 20, 2026	With provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for pytracer-registry 0.1.1
File	Interpreter	ABI	Platform	Reset
pytracer_registry-0.1.1-py3-none-any.whl 24.1 kB Oct 20, 2026 With provenance	Python 3	none	any	Details

Total release size: 48.2 kB

Release files / pytracer_registry-0.1.1.tar.gz

Download URL	pytracer_registry-0.1.1.tar.gz
Size	24.1 kB
Tags	Source
SHA-256 checksum How to use checksums	`0b21c74015b16ad58c6d078f4ff0f8e60a5d5bbf558f1473f26b9d5e81b9d290`
BLAKE2b-256 checksum How to use checksums	`c177d16a41d7987ea17ce971ca93f1e9f44211a24da9cc29099c3ae3c32b566a`
Upload date	Oct 20, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/vi6120/pyTracer
Publishing commit: github.com/vi6120/pyTracer/tree/a018cadaa69167dc4682dce6e6a642a55c3672e1

Workflow

Publishing configuration: github.com/vi6120/pyTracer/blob/a018cadaa69167dc4682dce6e6a642a55c3672e1/.github/workflows/publish.yml
Publishing logs: github.com/vi6120/pyTracer/actions/runs/39469884992/attempts/1

Artifact

Subject: pytracer_registry-0.1.1.tar.gz
SHA-256 checksum: 0b21c74015b16ad58c6d078f4ff0f8e60a5d5bbf558f1473f26b9d5e81b9d290 Verifying attestations

Release files / pytracer_registry-0.1.1-py3-none-any.whl

Download URL	pytracer_registry-0.1.1-py3-none-any.whl
Size	24.1 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`b03da10c6dd2e2d588846ce63c18f31dae063fd4f064eee2fc7988c0214e1075`
BLAKE2b-256 checksum How to use checksums	`fc88700182c3ba234d4cb267915aa027ef64be125cb0700123592e2a2821dfb4`
Upload date	Oct 20, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/vi6120/pyTracer
Publishing commit: github.com/vi6120/pyTracer/tree/a018cadaa69167dc4682dce6e6a642a55c3672e1

Workflow

Publishing configuration: github.com/vi6120/pyTracer/blob/a018cadaa69167dc4682dce6e6a642a55c3672e1/.github/workflows/publish.yml
Publishing logs: github.com/vi6120/pyTracer/actions/runs/39469884992/attempts/1

Artifact

Subject: pytracer_registry-0.1.1-py3-none-any.whl
SHA-256 checksum: b03da10c6dd2e2d588846ce63c18f31dae063fd4f064eee2fc7988c0214e1075 Verifying attestations

Security for pytracer-registry 0.1.1

Report project as malware

Provenance

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Attestation for pytracer_registry-0.1.1.tar.gz

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/vi6120/pyTracer
Publishing commit: github.com/vi6120/pyTracer/tree/a018cadaa69167dc4682dce6e6a642a55c3672e1

Workflow

Publishing configuration: github.com/vi6120/pyTracer/blob/a018cadaa69167dc4682dce6e6a642a55c3672e1/.github/workflows/publish.yml
Publishing logs: github.com/vi6120/pyTracer/actions/runs/39469884992/attempts/1

Artifact

Subject: pytracer_registry-0.1.1.tar.gz
SHA-256 checksum: 0b21c74015b16ad58c6d078f4ff0f8e60a5d5bbf558f1473f26b9d5e81b9d290 Verifying attestations

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.