Skip to main content

Tiramemsu: a brain taking a bite out of a tiramisu whose layers are a graph

tiramemsu

Your agent's brain loves Tiramemsu.
Layered, never-forget memory for agents, for Python.

Website · Time travel explained · Layered graphs explained · GitHub

Tiramemsu is an embedded graph database on SQLite. Every fact has its own id, so a fact can carry a confidence, a source or a belief about it, layer on layer. Every change is kept, with when the database learned it and when it was true in the world. This package is the Python binding: a native module (PyO3, stable ABI) and a typed, synchronous API.

Status: new. Tiramemsu was designed and implemented in September 2026. This package has not been published to PyPI yet, so the install line below works after the first release. Until then, build it from source.

Install

pip install tiramemsu

Python 3.9 or later. Each platform gets one prebuilt wheel (Linux x86_64 and aarch64, musllinux x86_64, macOS x86_64 and arm64, Windows x64), and SQLite is compiled in, so nothing else is needed. The package is typed (py.typed) and checked with mypy --strict.

Build from source instead

You need Python 3.9 or later and the Rust toolchain pinned by the repository (1.91.1).

git clone https://github.com/Volland/tiramemsu
cd tiramemsu/bindings/python
python3 -m venv .venv && source .venv/bin/activate
pip install maturin pytest mypy
maturin develop        # or: maturin develop --release
pytest

If another rustc is first on your PATH (for example Homebrew's), put rustup's first: export PATH="$HOME/.cargo/bin:$PATH".

Quick start

Alice joins Acme in 2020, with a confidence of 0.8. We later learn she left at the end of 2023, and then that she joined Globex in March 2024.

from tiramemsu import Database, Iri

V = "urn:tiramemsu:v:"  # written `v:` in queries
alice, works_at, acme, globex, confidence = (
    Iri(V + name) for name in ("alice", "worksAt", "acme", "globex", "confidence")
)

db = Database("memory.db")

# 1. A fact is a statement with its own id, so it can carry a layer.
with db.transact() as tx:
    job = tx.assert_(alice, works_at, acme, valid_from="2020-01-01")
    tx.assert_(job, confidence, 0.8)  # `job` is a Ref: the statement, before it has an id
first = tx.report.asserted[0]         # its eid, known once the transaction has committed

# 2. Correct it. The layer moves to the new statement; nothing is deleted.
with db.transact() as tx:
    tx.supersede(first, valid_to="2024-01-01")

# 3. A new fact.
with db.transact() as tx:
    tx.assert_(alice, works_at, globex, valid_from="2024-03-01")

# 4. Ask the same question at different times.
q = "SELECT ?org WHERE { v:alice v:worksAt ?org }"

def orgs(view):
    return [row["org"].value.rsplit(":", 1)[-1] for row in view.sparql(q)]

orgs(db.now())                                  # ['acme', 'globex']  both episodes are live
orgs(db.as_of(tx=1))                            # ['acme']            what we believed after tx 1
orgs(db.as_of(tx=1).valid_at("2026-01-01"))     # ['acme']            we thought she was still there
orgs(db.now().valid_at("2026-01-01"))           # ['globex']          what is true today
orgs(db.now().valid_at("2024-02-01"))           # []                  between the two jobs

The same store speaks Cypher, and a layer is a relationship property:

db.now().cypher("MATCH (a)-[r:worksAt]->(c) RETURN c, r.confidence AS conf")
# columns ['c', 'conf'], rows [[acme, 0.8], [globex, None]]  (Globex has no confidence layer)

Two clocks

A view chooses when you look and when the fact was true. Every read takes a view, and views are immutable.

You want Code
What we believe now db.now()
What we believed after transaction n db.as_of(tx=n)
What we believed at a wall-clock time db.as_of(instant="2026-09-01T12:00:00Z")
What was true on a date view.valid_at("2026-01-01")
Every statement ever, with retracted ones db.history()

valid_at combines with any of them. Valid time is off unless you ask for it. Time travel and bitemporality, explained has the full story.

Writing

db.transact() is a context manager. It records the operations of the block and commits them as one transaction when the block exits cleanly, and the report is on tx.report. If the block raises, nothing is committed. db.transact(ops) takes a list of operation dicts instead. assert_, create and supersede return a Ref that later calls in the same block accept as a statement id, a subject or an object.

Method What it does
assert_(s, p, o, valid_from=, valid_to=, on_existing=) Adds a statement; idempotent when a live one with an overlapping valid time exists
create(s, p, o, ...) Always adds one, for parallel edges
retract(eid) Ends belief in a statement and every layer about it
retract_matching(s=, p=, o=) Retracts every live match
supersede(eid, o=, valid_from=, valid_to=) Corrects a statement and replays its layers on the new one. A bound you leave out is kept; None clears it
confirm(eid) Records that another source agrees
meta(p, o), upsert(p, o), new_node() Transaction metadata, unique upsert, an anonymous node
add_to_graph(eid, g), remove_from_graph, clear_graph, create_graph, drop_graph Named graphs as tags on statements. A statement (Stmt(eid) or a Ref) can name a graph, so an edge can hold a subgraph
import_bundle(bundle) Imports a bundle from view.bundle, possibly read from another database; returns a Ref to the imported root, and its entry in tx.report.results lists the imported statements
cypher(text, params=None) A Cypher query that may write, inside the same transaction

Times accept a datetime, a date, epoch milliseconds or an RFC 3339 string. db.transact(dry_run=True) reports what would happen and commits nothing. db.speculate(ops, queries) applies changes hypothetically, runs queries on the result, and keeps nothing.

Reading

Method Returns
view.sparql(text, provenance=False, query_only=False, params=None, path_completeness=False) A select result (iterate it for rows of variable to term; .vars lists the variables, .provenance the statements behind each row, .provenance_gaps what they leave out, .path_completeness how completely the paths ran), an ask, a graph, or an update result
view.cypher(text, params=None, path_completeness=False) A result with columns, rows and path_completeness
view.triples(s=, p=, o=) Statement values with eid, s, p, o, t_add, t_ret, valid_from, valid_to, ret_kind
view.path(start, expr, mode="reach", max_hops=None, graphs=None, time_respecting=False, capped=False) Endpoints with hop counts and arrival. mode is "reach", "trail", "anyShortest" or "allShortest"
view.path_report(start, expr, ...) PathReport(rows, completeness): the rows of path and a PathCompleteness
view.dependents(eid) The statements that stand on eid: what retracting it would cascade to
view.bundle(eid) The statement with its layers and evidence, as a tiramemsu-bundle/1 dict
view.conflicts(s=, p=, limit=, confidence=, source=) Conflicts: overlapping distinct values with overlaps and each statement's ConflictEvidence; nothing is written
view.events(since=0) The change log after a transaction
view.graphs(), view.graph_members(g), view.values(s, key) Named graphs and values

expr is SPARQL property-path syntax with the predeclared prefixes v:, sys:, tm:, rdf: and xsd:, for example v:knows+. SPARQL supports RDF 1.2 annotations: {| v:confidence ?c |} reads a layer.

With provenance=True a select result's .provenance holds, for each row, the Stmt values that produced it, and .provenance_gaps lists the query parts whose statements are not cited (["recursivePath"] for a + or * path; empty means complete). query_only=True makes an update raise Unsupported before anything runs. graphs keeps every hop of a path inside the listed graphs. time_respecting=True (or a time to start after) makes each hop start no earlier than the previous one, and every row then carries its earliest arrival in epoch milliseconds.

The query languages say the same with opt-in extensions. SPARQL: SERVICE <urn:tiramemsu:tm:timeRespecting/$since> { v:a v:met+ ?who . ?who tm:arrival ?t } with params={"since": 2} (the start may also be written as epoch ms or an xsd:date/xsd:dateTime after the slash, or left out for −∞; ?t is unbound for −∞). Cypher: MATCH TIME RESPECTING AFTER $since ARRIVAL AS t (a {`@id`: 'v:a'})-[:met*]->(who) RETURN who, t (AFTER takes an integer, a parameter, datetime('…') or date('…'); t is None for −∞). Both need the start bound, and the rows keep their columns unless the arrival is asked for.

path_completeness=True (and path_report) report a frozen PathCompleteness(kind, max_hops, complete): kind is "exhaustive", "bound" (an explicit hop bound stopped the search; complete within it) or "cap" (the database's path_max_hops cut an unbounded pattern such as a Cypher *; longer paths may exist), and capped=True applies that cap to path. A search over path_max_states raises PathLimitExceeded.

Terms

Python Stored as
str, bool plain string, boolean
int xsd:integer, exact at any size
float xsd:double
datetime, date xsd:dateTime, xsd:date; they come back as the same Python types. A naive datetime is taken as UTC
Iri(s) IRI
Literal(lex, datatype=), Literal(lex, lang=) typed or language-tagged literal
Node(n), BNode(n), Stmt(eid), TxId(n) anonymous node, blank node, statement id, transaction

Errors

Every failure raises TiramemsuError with a .code:

Code Meaning
Parse SPARQL, Cypher or path text is invalid
InvalidArgument The call itself is malformed: an unknown operation, a missing field, a term of the wrong shape
NotLive The statement does not exist or was already retracted
Unsupported Valid but outside the supported subset, such as a Cypher write through a read view
UniqueViolation A sys:unique predicate already has a live holder of that value
ValueTypeMismatch The object does not match the predicate's sys:valueType
SubjectTypeMismatch The subject does not match the predicate's sys:subjectType, such as a layer predicate on a plain node
CascadeLimitExceeded A retraction would touch more than max_cascade statements
PathLimitExceeded A path search exceeded its state limit
DeadlineExceeded A budgeted call ran past its timeout_ms
Cancelled A budgeted call was stopped with db.cancel(key)
PoolTimeout No reader became free within reader_timeout_ms
ResultLimitExceeded A budgeted call decoded more than max_rows rows or max_bytes bytes
InvalidPatch A supersede patch tried to change the subject or predicate
IdSpaceExhausted An id counter passed 2^48 − 1
ImportInProgress A write, or a second import session, while a bulk import session is open
TextIndexUnavailable text_search before the text index was built (text_index=True or rebuild_text_index())
MissingCapability text_search on a SQLite without FTS5
SavedAnswerNotFound refresh_answer of a name that was never saved
Sqlite A SQLite failure, such as a locked or unreadable file

Options

Database(path, readers=, busy_timeout_ms=, term_cache_capacity=, optimize_every=, path_max_hops=, path_max_states=, reader_timeout_ms=, text_index=, lftj=, lftj_min_rows=). It works as a context manager, and Python threads can query one Database in parallel, because the GIL is released during each call.

lftj=True routes pure cyclic patterns (triangles and longer cycles) to the native leapfrog-triejoin operator once some pattern matches at least lftj_min_rows statements (default 100000; 0 = always). Results are the same either way; view.explain_sparql(text) shows the route and, when a region stayed in SQL, why:

db = Database("memory.db", lftj=True, lftj_min_rows=0)
plan = db.now().explain_sparql("SELECT * WHERE { ?a v:knows ?b . ?b v:knows ?c . ?c v:knows ?a }")
[(r["kind"], r["note"]) for r in plan["regions"]]  # [("nativeLftj", "lftjNative"), ...]

Budgets

Calls are unbounded by default. A QueryBudget bounds one call: timeout_ms, reader_timeout_ms, max_rows and max_bytes (counted across every statement the call runs), and cancel_key. A stopped write commits nothing, and an over-budget result raises instead of returning a prefix.

from tiramemsu import QueryBudget

view = db.now().with_budget(QueryBudget(timeout_ms=500, max_rows=10_000))
view.sparql("SELECT ?o WHERE { <urn:ex:alice> <urn:ex:worksAt> ?o }")

with db.transact(budget=QueryBudget(timeout_ms=1_000)) as tx:
    tx.assert_(alice, works_at, acme)

# from another thread: stop the call running with cancel_key="job-42"
db.cancel("job-42")

Text recall

Recall statements by the words in their string values. Build the index with text_index=True (or db.rebuild_text_index()); every write then keeps it current.

db = Database("memory.db", text_index=True)
with db.transact() as tx:
    note = tx.assert_(alice, Iri("urn:tiramemsu:v:note"), "met at the Lisbon offsite")
    tx.assert_(note, Iri("urn:tiramemsu:v:confidence"), 0.9)

for hit in db.now().text_search("lisbon offsite", limit=10):
    print(hit.rank, hit.score, hit.text, hit.evidence.confidence)  # confidence is None when absent

db.now().sparql('SELECT ?e WHERE { ?e tm:textMatch "lisbon" }')
db.now().cypher("CALL tiramemsu.text.search('lisbon') YIELD statement, score RETURN statement, score")

text_search(text, mode="all"|"any"|"phrase", graphs=, predicates=, limit=, confidence=) returns TextHits ranked by lexical score, then confidence, confirmations, authors and recency, then eid. Views apply: db.as_of(...) recalls what was believed then.

Conflict review

for c in db.now().conflicts(p=Iri("urn:tiramemsu:v:worksAt")):
    print(c.s, c.overlaps, [(v.o, [e.authors for e in v.statements]) for v in c.values])
preview = db.preview_bundle(bundle)       # dry run: nothing committed
if preview.would_commit:
    with db.transact() as tx:
        tx.import_bundle(bundle)          # validates again

preview.failure holds a schema failure ({"code", "message"}) instead of raising it; preview.burned and preview.scope say which ids the dry run burned and which transaction it read. conflicts raises Unsupported on the history view.

Saved answers

Save a query's answer and let later writes mark it. A retracted or superseded cited statement makes it "stale"; any other write under a current view makes it "recheck"; only a successful refresh_answer makes it "fresh" again.

db.save_answer("employer", "SELECT ?o WHERE { v:alice v:worksAt ?o }")
db.save_answer("then", "MATCH (p)-[:worksAt]->(c) RETURN count(*) AS n",
               language="cypher", view=db.as_of(tx=1))
with db.transact() as tx:
    tx.assert_(alice, works_at, globex)
for m in db.check_saved_answers():       # each invalidation is reported once
    print(m.name, m.status, m.cause, m.event)
a = db.refresh_answer("employer")        # SavedAnswer: status, result, dependencies, coverage, ...

saved_answer(name) and saved_answers() read the records, delete_saved_answer(name) removes one, and save_answer / refresh_answer take budget=. A failed refresh raises and keeps the old result, mark and checkpoint (error says why); an unknown name raises SavedAnswerNotFound.

Bulk import

db.bulk_import() starts a session for large loads: each chunk is one atomic transaction (a context manager or a list of op dicts, with the options of transact), chunks skip the per-commit statistics refresh, and finishing runs one full analysis. A failing chunk raises and rolls back alone; earlier chunks stay. While the session is open other writes raise ImportInProgress and reads see the last committed chunk.

with db.bulk_import() as imp:          # finishes on a clean exit, cancels if the block raises
    for batch in batches:
        with imp.chunk() as tx:
            for s, p, o in batch:
                tx.assert_(s, p, o)
print(imp.summary.progress.chunks, imp.summary.analyzed, imp.summary.maintenance_error)

imp.progress() returns an ImportProgress (chunks, rejected, asserted, existing, retracted, txs, elapsed_ms, maintenance_ms); imp.finish() returns an ImportSummary, and a failed final analysis is its maintenance_error, never a rollback. imp.cancel() ends the session without analysis; db.info()["statisticsDue"] then stays true until the next write or db.optimize().

Good to know

  • The API is synchronous, like the Rust core. Reads run in parallel on a small connection pool, and writes serialize on one writer.
  • Nothing is ever deleted: the SQLite file rejects DELETE. Forgetting means retracting, and the past stays exact.
  • Results cross the native boundary as JSON, which is fine for agent memory and not meant for million-row result sets.
  • There is no network server. For agents, the separate tiramemsu-mcp crate serves a database file over MCP (stdio), and tm-wasm runs the engine in the browser.

License

MIT OR Apache-2.0, at your option. See LICENSE-MIT and LICENSE-APACHE.

Metadata

Release files for tiramemsu 0.6.0

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

Source distribution (sdist)

Source distribution for tiramemsu 0.6.0
File Size Uploaded Provenance Actions
tiramemsu-0.6.0.tar.gz 890.5 kB With provenance Details for tiramemsu-0.6.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for tiramemsu 0.6.0
File Actions
tiramemsu-0.6.0-cp39-abi3-win_amd64.whl CPython 3.9 abi3 Windows x86-64 Details for tiramemsu-0.6.0-cp39-abi3-win_amd64.whl
tiramemsu-0.6.0-cp39-abi3-musllinux_1_2_x86_64.whl CPython 3.9 abi3 Linux musl 1.2+ x86-64 Details for tiramemsu-0.6.0-cp39-abi3-musllinux_1_2_x86_64.whl
tiramemsu-0.6.0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.9 abi3 Linux glibc 2.17+ x86-64 Details for tiramemsu-0.6.0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
tiramemsu-0.6.0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.9 abi3 Linux glibc 2.17+ ARM64 Details for tiramemsu-0.6.0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
tiramemsu-0.6.0-cp39-abi3-macosx_11_0_arm64.whl CPython 3.9 abi3 macOS 11.0+ ARM64 Details for tiramemsu-0.6.0-cp39-abi3-macosx_11_0_arm64.whl
tiramemsu-0.6.0-cp39-abi3-macosx_10_12_x86_64.whl CPython 3.9 abi3 macOS 10.12+ x86-64 Details for tiramemsu-0.6.0-cp39-abi3-macosx_10_12_x86_64.whl

Total release size: 35.8 MB

Release files / tiramemsu-0.6.0.tar.gz

Download URL tiramemsu-0.6.0.tar.gz
Size 890.5 kB
Tags Source
SHA-256 checksum
How to use checksums
780b5e1c54699b974c1bd9e6b1a7df9245c21b8b9255b40b9ed73821f1d93ad7
BLAKE2b-256 checksum
How to use checksums
e5a7c2123ebcb72f3d468da2688713a1637eb1681aa3ea498897f742e2f34143
Upload date
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.

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 12, 2026.

Transparency log

Release files / tiramemsu-0.6.0-cp39-abi3-win_amd64.whl

Download URL tiramemsu-0.6.0-cp39-abi3-win_amd64.whl
Size 5.5 MB
Tags CPython 3.9 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
d161f986040cfc3aa2e43eb883e294927ab4f63930959b3246313e41b47d09eb
BLAKE2b-256 checksum
How to use checksums
d3ebae941dee749c0a6c61d056b172d52994fd17d7de540defc1e088953a6976
Upload date
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.

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 12, 2026.

Transparency log

Release files / tiramemsu-0.6.0-cp39-abi3-musllinux_1_2_x86_64.whl

Download URL tiramemsu-0.6.0-cp39-abi3-musllinux_1_2_x86_64.whl
Size 6.3 MB
Tags CPython 3.9 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
92f572d60b2dfc8aeb66508da6c874e77f3ef200b0bd60ced53f9907047272c7
BLAKE2b-256 checksum
How to use checksums
d34ce70681aa09a4b06f75b2e6653b6408323db3b8efb48e8ea2f6b20e2788ab
Upload date
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.

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 12, 2026.

Transparency log

Release files / tiramemsu-0.6.0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL tiramemsu-0.6.0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 6.1 MB
Tags CPython 3.9 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
51fc14b56c612b0d9e4aa0c1f95e2191551d73a698dd4c01d8ddee8568094b03
BLAKE2b-256 checksum
How to use checksums
d858989c6fff320755899e56100db809a856eb1029f3c86d4f7cb397cc2091c7
Upload date
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.

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 12, 2026.

Transparency log

Release files / tiramemsu-0.6.0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL tiramemsu-0.6.0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 5.8 MB
Tags CPython 3.9 Linux glibc 2.17+ ARM64 abi3
SHA-256 checksum
How to use checksums
124cfb7cd9c5215dc9b7929d7eca5382c1f2cf71edcac2adad747c3fbf13d041
BLAKE2b-256 checksum
How to use checksums
e7fc5d1bc0fe65ac0a608ddcdee6385750393e2fe0f6b99b5ced29cd975f95be
Upload date
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.

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 12, 2026.

Transparency log

Release files / tiramemsu-0.6.0-cp39-abi3-macosx_11_0_arm64.whl

Download URL tiramemsu-0.6.0-cp39-abi3-macosx_11_0_arm64.whl
Size 5.4 MB
Tags CPython 3.9 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
50da56f714d8424d54c5bccc8f890a759f407e41fbfb3f20ae299521b9f51d1d
BLAKE2b-256 checksum
How to use checksums
bf83845ec258e0e868b257b64bef62d58b7ae5c3122e85bbd906062df1dbb4a4
Upload date
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.

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 12, 2026.

Transparency log

Release files / tiramemsu-0.6.0-cp39-abi3-macosx_10_12_x86_64.whl

Download URL tiramemsu-0.6.0-cp39-abi3-macosx_10_12_x86_64.whl
Size 5.7 MB
Tags CPython 3.9 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
6a99e63fe07db2909c5232910e97899acb1c1cde0e301c7c1714496f05ae3f4b
BLAKE2b-256 checksum
How to use checksums
0fcc800f831ef741063fc7d1d3c7f10cf138c082ee5860400b51ed9015bb3b75
Upload date
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.

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 12, 2026.

Transparency log

Security for tiramemsu 0.6.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 7 files in this release have been uploaded with provenance metadata.

Select from 7 files

Attestation for tiramemsu-0.6.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 12, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page