Change of provenance

The repository or configuration that created this release differ from a previous release. View details.

outcome-engineering (api)

Server-side package: domain core (oe_core), Postgres store (oe_store), FastAPI service (oe_api), MCP service (oe_mcp), and the oe CLI (oe_cli). See the repository root README for the full picture.

Metadata

Release files for outcome-engineering 0.1.3

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

Change of provenance

The repository or configuration that created these release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Source distribution (sdist)

Source distribution for outcome-engineering 0.1.3
File	Size	Uploaded	Provenance
outcome_engineering-0.1.3.tar.gz	146.7 kB	Jul 3, 2026	With provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for outcome-engineering 0.1.3
File	Interpreter	ABI	Platform	Reset
outcome_engineering-0.1.3-py3-none-any.whl 50.5 kB Jul 3, 2026 With provenance	Python 3	none	any	Details

Total release size: 197.2 kB

Release files / outcome_engineering-0.1.3.tar.gz

Change of provenance

This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Download URL	outcome_engineering-0.1.3.tar.gz
Size	146.7 kB
Tags	Source
SHA-256 checksum How to use checksums	`fa56c1c70b1eae8561a7398dacf378e3a78ef6cb0203365f69b553eb91ba15a0`
BLAKE2b-256 checksum How to use checksums	`a577c47471a7e5ae40e48ad0b8e462a354fd51584cab1bd1f520616a3aed1f4f`
Upload date	Jul 3, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.13.12`

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/computerlovetech/outcome-engineering
Publishing commit: github.com/computerlovetech/outcome-engineering/tree/f7d7d60198fbfc74fe5929b4f9abb0aa2fafd9b3

Workflow

Publishing configuration: github.com/computerlovetech/outcome-engineering/blob/f7d7d60198fbfc74fe5929b4f9abb0aa2fafd9b3/.github/workflows/publish.yml
Publishing logs: github.com/computerlovetech/outcome-engineering/actions/runs/28679857309/attempts/1

Artifact

Subject: outcome_engineering-0.1.3.tar.gz
SHA-256 checksum: fa56c1c70b1eae8561a7398dacf378e3a78ef6cb0203365f69b553eb91ba15a0 Verifying attestations

Release files / outcome_engineering-0.1.3-py3-none-any.whl

Change of provenance

This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Download URL	outcome_engineering-0.1.3-py3-none-any.whl
Size	50.5 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`dfdff09b47b5afde17144ec549ffe8151b9f644aa7d1e5bff9c10d31d69230b3`
BLAKE2b-256 checksum How to use checksums	`ce3f6e8ea166f07b431c3099c9e579e9de92e11c0a2c4494547e551ab3c9e631`
Upload date	Jul 3, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.13.12`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/computerlovetech/outcome-engineering
Publishing commit: github.com/computerlovetech/outcome-engineering/tree/f7d7d60198fbfc74fe5929b4f9abb0aa2fafd9b3

Workflow

Publishing configuration: github.com/computerlovetech/outcome-engineering/blob/f7d7d60198fbfc74fe5929b4f9abb0aa2fafd9b3/.github/workflows/publish.yml
Publishing logs: github.com/computerlovetech/outcome-engineering/actions/runs/28679857309/attempts/1

Artifact

Subject: outcome_engineering-0.1.3-py3-none-any.whl
SHA-256 checksum: dfdff09b47b5afde17144ec549ffe8151b9f644aa7d1e5bff9c10d31d69230b3 Verifying attestations

Security for outcome-engineering 0.1.3

Report project as malware

Provenance

Change of provenance

The repository that created this release differs from a previous release.

While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.

Repository

Removed 0.1.2 GitHub: kasperjunge/outcome-engineering
Added 0.1.3 GitHub: computerlovetech/outcome-engineering

Attestation for outcome_engineering-0.1.3.tar.gz

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/computerlovetech/outcome-engineering
Publishing commit: github.com/computerlovetech/outcome-engineering/tree/f7d7d60198fbfc74fe5929b4f9abb0aa2fafd9b3

Workflow

Publishing configuration: github.com/computerlovetech/outcome-engineering/blob/f7d7d60198fbfc74fe5929b4f9abb0aa2fafd9b3/.github/workflows/publish.yml
Publishing logs: github.com/computerlovetech/outcome-engineering/actions/runs/28679857309/attempts/1

Artifact

Subject: outcome_engineering-0.1.3.tar.gz
SHA-256 checksum: fa56c1c70b1eae8561a7398dacf378e3a78ef6cb0203365f69b553eb91ba15a0 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.