Skip to main content
Incomplete provenance

3 of 9 release files were uploaded without provenance metadata. View details.

GLLM Memory

Description

Memory layer for AI agents. The public API is MemoryManager. You can use it in two ways:

  1. HTTP mode: use api_key and optional host
  2. SDK mode: use MemoryManagerConfig and pass config=...

In SDK mode, you can register your own LLM, embedding model, memory store, and optional reranker without exposing backend-specific config to application code.

TL;DR / 30-Second Example

Fastest HTTP mode example:

from gllm_inference.schema.message import Message
from gllm_memory import MemoryManager
from gllm_memory.enums import MemoryScope

memory_manager = MemoryManager(api_key="your_mem0_api_key")

await memory_manager.add(
    user_id="user_123",
    agent_id="agent_456",
    messages=[Message.user("I love pizza")],
    scopes={MemoryScope.USER},
)

results = await memory_manager.search(
    query="What does the user like?",
    user_id="user_123",
    scopes={MemoryScope.USER},
)

For the recommended SDK mode setup with MemoryManagerConfig, see SDK Mode.

Installation & Setup

Requirements

  1. Python 3.11+ — Install here
  2. pip or uv — pip, uv
  3. gcloud CLI — Install here
  4. Git — only needed for local development from a cloned repository

Authentication

Use this once when you need internal packages or local development setup:

gcloud auth login
export UV_INDEX_GEN_AI_INTERNAL_USERNAME=oauth2accesstoken
export UV_INDEX_GEN_AI_INTERNAL_PASSWORD="$(gcloud auth print-access-token)"
export UV_INDEX_GEN_AI_USERNAME=oauth2accesstoken
export UV_INDEX_GEN_AI_PASSWORD="$(gcloud auth print-access-token)"

Install from Artifact Registry

uv pip install \
  --extra-index-url "https://oauth2accesstoken:$(gcloud auth print-access-token)@glsdk.gdplabs.id/gen-ai-internal/simple/" \
  gllm-memory

Install from Local Clone

git clone git@github.com:GDP-ADMIN/gl-sdk.git
cd gl-sdk/libs/gllm-memory
pip install -e .

For the full local development setup with project tooling:

make setup
source .venv/bin/activate

Runtime Notes

  1. HTTP mode uses MEM0_API_KEY and optional MEM0_HOST.
  2. SDK mode uses MemoryManagerConfig(...) and lets your app register LM, embedding, memory store, and optional retrieval reranker.

Optional Dependencies

  1. OpenAI-based SDK examples require OpenAI support from gllm-inference, for example gllm-inference[openai].
  2. Knowledge graph examples require the KG dependencies used by this repository setup.

Typical environment variables:

Variable Role
MEM0_API_KEY Required for the HTTP client when not passed in code.
MEM0_HOST Optional; base URL for self-hosted Mem0 API.
MEMORY_PROVIDER Optional; default is Mem0 (mem0).
MEMORY_RETENTION_ENABLED Optional; enables vector-memory and persistent Mem0 SQLite history retention (default false).
MEMORY_DEDUP_ENABLED Optional; enables semantic dedupe on the retention schedule (default false).
MEMORY_DEDUP_SIMILARITY_THRESHOLD Optional; embedding similarity threshold for dedupe (default 0.65).
MEMORY_RETENTION_CRON_DAY Optional; retention and enabled-dedupe schedule day (default sat).
MEMORY_RETENTION_CRON_HOUR Optional; retention and enabled-dedupe hour in server-local time (default 1).
MEMORY_RETENTION_CRON_MINUTE Optional; retention and enabled-dedupe minute in server-local time (default 0).
MEMORY_RETENTION_DAYS Optional; shared vector-memory and SQLite history age in days (default 90).
MEMORY_DEDUP_LOOKBACK_DAYS Optional; recent-window scan using created_at OR updated_at (default 7).
MEMORY_DEDUP_MAX_CANDIDATES_PER_ANCHOR Optional; per-anchor semantic search cap (default 100).
MEMORY_DEDUP_MAX_TARGET_MEMORIES Optional; per-partition safeguard before the job skips a large target (default 5000).
TIMEOUT_SEC Optional; request timeout in seconds (default 30). Used when building clients from env.

Do not commit secrets to git.

Error Handling

Public configuration and provider failures use typed errors with stable GLLM-MEM-* codes. Applications can use error.code to select a user-facing message without depending on provider-specific exception text.

See the Error Code Catalog for each code, its trigger, and recommended recovery action.

Relevant errors also include recovery metadata. Check recovery.retryable before retrying. Retryable errors use the caller_owned policy: the caller sets the retry limit and backoff. When present, wait at least recovery.retry_after_seconds before retrying and use recovery.escalate_when to decide when to escalate the failure.

For public-boundary behavior and documented exceptions, see the Error Boundary Audit.

Semantic Memory Dedupe

gllm-memory includes one internal background maintenance job for retrieval-based vector retention, semantic dedupe, and persistent Mem0 SQLite audit-history retention.

You do not call this job directly from MemoryManager. When memory maintenance is enabled, the scheduler is registered automatically during MemoryManager initialization.

What it does:

  1. scans recent memories from the configured vector store
  2. groups candidates inside one partition: scope + user_id + agent_id + source + target
  3. finds semantically similar memories using embedding similarity
  4. keeps one canonical memory and removes duplicate rows when it is safe
  5. hard-deletes non-important vector memories that have not been retrieved for MEMORY_RETENTION_DAYS
  6. removes persistent Mem0 SQLite audit-history events older than MEMORY_RETENTION_DAYS

Safety rules in the current implementation:

  1. is_important=True memories are never deleted
  2. canonical priority is: important > newer > richer content > older
  3. if compatible memories are in the same context, the canonical memory can be updated with merged content before duplicate rows are deleted
  4. if custom metadata conflicts, that duplicate group is skipped
  5. deletion is hard delete from the vector store

Current behavior:

  1. the first version uses embedding-only comparison
  2. retention runs only when MEMORY_RETENTION_ENABLED=true; semantic dedupe runs only when MEMORY_DEDUP_ENABLED=true
  3. the default schedule is Saturday at 01:00
  4. the timezone follows the server-local timezone where gllm-memory runs
  5. the default lookback window is the last 7 days using created_at OR updated_at
  6. the default large-partition safeguard is MEMORY_DEDUP_MAX_TARGET_MEMORIES=5000
  7. the in-process registry prevents duplicate local schedulers and Elasticsearch lease ownership permits one active run per vector-store target across pods
  8. the current full-store scanner implementation is available for Elasticsearch-backed vector stores
  9. SQLite history retention runs only for persistent SDK history_db_path; it skips in-memory history and does not automatically run VACUUM

Architecture

The system follows a layered architecture below:

┌──────────────────────────────────────────────────────────────┐
│                    Application Layer                         │
├──────────────────────────────────────────────────────────────┤
│                    Memory Manager                            │
├──────────────────────────────────────────────────────────────┤
│                    Memory Client (Base)                      │
├──────────────────────────────────────────────────────────────┤
│                    Provider Layer (Mem0)                     │
├──────────────────────────────────────────────────────────────┤
│                    Mem0 Platform (HTTP client or Python SDK) │
└──────────────────────────────────────────────────────────────┘

🧩 SDK Mode With MemoryManagerConfig

Use this mode if you want to:

  1. register memory LLM and embedding invoker runtimes
  2. configure an optional reranker
  3. keep application code independent from backend-specific config shape

gllm-memory does not create provider-specific LM or embedding invokers for you in normal SDK usage. Your application builds the LM invoker, optional fallback invokers, one embedding invoker, and then wraps the memory LLM path with the library-owned MemoryLMComponent.

SDK Mode Example

Recommended LLM registration:

from gllm_inference.lm_invoker.lm_invoker import BaseLMInvoker
from gllm_inference.lm_invoker.openai_lm_invoker import OpenAILMInvoker
from gllm_memory import MemoryLMComponent, MemoryManagerConfig


def build_openai_lm_invoker(model_name: str) -> OpenAILMInvoker:
    return OpenAILMInvoker(
        model_name=model_name,
        api_key="your_openai_api_key",
    )


def build_fallback_lm_invokers() -> list[BaseLMInvoker]:
    return [
        build_openai_lm_invoker("gpt-4o-mini"),
    ]


def build_lm_component() -> MemoryLMComponent:
    return MemoryLMComponent(
        lm_invoker=build_openai_lm_invoker("gpt-5-nano"),
        fallback_lms=build_fallback_lm_invokers() or None,
    )


def build_em_invoker():
    from gllm_inference.em_invoker.openai_em_invoker import OpenAIEMInvoker

    return OpenAIEMInvoker(
        model_name="text-embedding-3-small",
        api_key="your_openai_api_key",
    )


lm_component = build_lm_component()
em_invoker = build_em_invoker()

config = (
    MemoryManagerConfig.builder()
    .memory_store.elasticsearch(
        host="localhost",
        port=9200,
        collection_name="memories",
        embedding_model_dims=1536,
    )
    .embedding.register(
        em_invoker,
        embedding_dims=1536,
    )
    .llm.register_component(lm_component)
    .reranker.similarity_based(
        em_invoker,
        top_k=5,
    )
    .build()
)

In this path, em_invoker and the underlying LM invokers are created by your application, while MemoryLMComponent is owned by gllm-memory. MemoryManager.instruction remains the source of truth for memory extraction instructions, and lm_component can route from one primary LM to fallback_lms when the primary LM fails.

The reranker is optional. If you do not need retrieval reranking, omit .reranker.similarity_based(...) from the builder. When configured with similarity_based(...), reranking runs in the external retrieval layer after provider retrieval returns chunks. The provider keeps native backend rerank disabled for this path so the request does not run double reranking. If your installed gllm_inference version still has a circular import on OpenAIEMInvoker, instantiate the EM invoker with a local lazy import like the example above.

SDK Mode With Default Config

If you want to use the default SDK setup, you can build an empty config:

from gllm_memory import MemoryManager, MemoryManagerConfig

config = MemoryManagerConfig.builder().build()
memory_manager = MemoryManager(config=config)

Default SDK behavior:

  1. memory store uses Elasticsearch
  2. embedding uses gllm-inference: EM Invoker with OpenAI defaults
  3. llm uses gllm-inference OpenAI defaults
  4. reranker is omitted unless configured explicitly

Required environment variables for the default SDK config:

  1. ELASTICSEARCH_HOST
  2. ELASTICSEARCH_PORT
  3. ELASTICSEARCH_COLLECTION_NAME
  4. ELASTICSEARCH_EMBEDDING_MODEL_DIMS
  5. OPENAI_API_KEY

Optional environment variables:

  1. ELASTICSEARCH_USER
  2. ELASTICSEARCH_PASSWORD
  3. OPENAI_BASE_URL
  4. OPENAI_MODEL_NAME (default SDK LLM model override)
  5. OPENAI_EMBEDDING_MODEL (used by examples/example_mem0_sdk_client.py)
  6. MEMORY_RETENTION_ENABLED (default false)
  7. MEMORY_RETENTION_CRON_DAY (default sat)
  8. MEMORY_RETENTION_CRON_HOUR (default 1)
  9. MEMORY_RETENTION_CRON_MINUTE (default 0)
  10. MEMORY_RETENTION_DAYS (default 90)
  11. MEMORY_DEDUP_ENABLED (default false)
  12. MEMORY_DEDUP_SIMILARITY_THRESHOLD (default 0.65)

Elasticsearch transport safety:

  1. A host that already includes http:// or https:// keeps that scheme.
  2. A hostname-only config that omits use_ssl uses the SDK default, which is HTTP.
  3. For a hostname-only HTTPS deployment, set use_ssl=True explicitly in the Elasticsearch memory-store config.

🌐 HTTP Mode

Use this mode if you want to connect to the HTTP API directly. Point the client at your own server:

from gllm_memory import MemoryManager

manager = MemoryManager(
    api_key="your-api-key",
    host="https://your-mem0-server.com",
)

If you want local SDK mode, use MemoryManager(config=...) instead of api_key and host.

HTTP Mode Example

from gllm_inference.schema.message import Message
from gllm_memory import MemoryManager
from gllm_memory.enums import MemoryScope

memory_manager = MemoryManager(api_key="...", host="...")  # host optional

messages = [
    Message.user("I love pizza"),
    Message.assistant("Noted."),
]
await memory_manager.add(
    user_id="user_123",
    agent_id="agent_456",
    messages=messages,
    scopes={MemoryScope.USER},
    metadata={"conversation_id": "chat_001"},  # Optional
    infer=True,  # Optional, defaults to True
    is_important=False,  # Optional, defaults to False
)

memories = await memory_manager.search(
    query="What does the user like?",
    user_id="user_123",
    scopes={MemoryScope.USER},
    metadata=None,  # Optional
    threshold=0.3,  # Optional, defaults to 0.3
    top_k=10,  # Optional, defaults to 10
    include_important=False,  # Optional, defaults to False
    rerank=False,  # Optional, defaults to False; if True, applies re-ranking to results
)

🕸️ Knowledge Graph in GLLM Memory

gllm-memory can optionally use a Knowledge Graph (KG) so one search flow can combine:

  1. normal memory retrieval
  2. graph-based facts such as people, companies, places, and relationships

Enable it with the same public API:

memory_manager = MemoryManager(config=config)

Recommended setup:

from gllm_inference.lm_invoker.openai_lm_invoker import OpenAILMInvoker
from gllm_memory import MemoryManager, MemoryManagerConfig, Neo4jGraphStoreConfig

memory_lm_component = build_lm_component()
em_invoker = build_em_invoker()

kg_lm_invoker = OpenAILMInvoker(
    model_name="gpt-4o-mini",
    api_key="your_openai_api_key",
)

config = (
    MemoryManagerConfig.builder()
    .memory_store.elasticsearch(
        host="localhost",
        port=9200,
        collection_name="memories",
        embedding_model_dims=1536,
    )
    .embedding.register(
        em_invoker,
        embedding_dims=1536,
    )
    .llm.register_component(memory_lm_component)
    .knowledge_graph.enable(
        lm_invoker=kg_lm_invoker,
        graph_store=Neo4jGraphStoreConfig(
            uri="bolt://localhost:7687",
            user="neo4j",
            password="password",
        ),
    )
    .build()
)

memory_manager = MemoryManager(config=config)

MemoryManager enables KG automatically when the config contains a knowledge_graph section.

Detailed KG flows, storage isolation, update behavior, and delete behavior are documented in docs/knowledge-graph.md.

Core API methods

MemoryManager exposes async methods; query is required where noted.

Usage examples:

  1. SDK mode example: see SDK Mode With MemoryManagerConfig
  2. HTTP mode example: see 🌐 HTTP Mode

Methods

  • add(user_id, agent_id, messages, scopes, metadata, infer, is_important) -> list[Chunk] - Add new memories from message objects.
  • search(query, user_id, agent_id, scopes, metadata, threshold, top_k, include_important, rerank) -> list[Chunk] - Search and retrieve memories by query.
  • list_memories(user_id, agent_id, scopes, metadata, keywords, page, page_size) -> list[Chunk] - Get memories with pagination and optional keyword filtering.
  • update(memory_id, new_content, metadata, user_id, agent_id, scopes, is_important) -> Chunk | None - Update one existing memory by ID.
  • delete(memory_ids, user_id, agent_id, scopes, metadata) -> list[Chunk] - Delete memories by IDs or by user or agent identifiers. When KG is enabled, the related KG contribution is also cleaned up.
  • delete_by_user_query(query, user_id, agent_id, scopes, metadata, threshold, top_k) -> list[Chunk] - Delete memories by query. When KG is enabled, the related KG contribution is also cleaned up.

🔧 Code Quality

# Format code with ruff
ruff format gllm_memory/ tests/

# Check code quality
ruff check gllm_memory/ tests/

# Fix auto-fixable issues
ruff check gllm_memory/ tests/ --fix

Local Development Utilities

The following Makefile commands are available for quick operations:

Install uv

make install-uv

Install Pre-Commit

make install-pre-commit

Install Dependencies

make install

Update Dependencies

make update

Run Tests

make test

Contributing

Please refer to the Python Style Guide for information about code style, documentation standards, and SCA requirements.

Contributing Steps

  1. Fork and clone the repository

  2. Set up development environment:

    # Complete setup: installs uv, configures auth, installs packages, sets up pre-commit
    make setup
    
  3. Activate virtual environment:

    source .venv/bin/activate
    
  4. Run tests to ensure everything works:

    make test
    
  5. Make your changes and ensure tests pass:

    # Make your changes
    # Ensure tests pass
    make test
    
  6. Submit a pull request:

    # Submit a pull request
    git push origin your-branch
    

Metadata

Release files for gllm-memory-binary 0.3.7.post2

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

Incomplete provenance

3 of 9 files were uploaded without provenance metadata.

We recommend further investigation before installing these files. View details.

Built distributions (wheels)

Table of built distributions (wheels) for gllm-memory-binary 0.3.7.post2
File Actions
gllm_memory_binary-0.3.7.post2-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for gllm_memory_binary-0.3.7.post2-cp313-cp313-win_amd64.whl
gllm_memory_binary-0.3.7.post2-cp313-cp313-manylinux_2_31_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.31+ x86-64 Details for gllm_memory_binary-0.3.7.post2-cp313-cp313-manylinux_2_31_x86_64.whl
gllm_memory_binary-0.3.7.post2-cp313-cp313-macosx_13_0_arm64.whl CPython 3.13 CPython 3.13 macOS 13.0+ ARM64 Details for gllm_memory_binary-0.3.7.post2-cp313-cp313-macosx_13_0_arm64.whl
gllm_memory_binary-0.3.7.post2-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for gllm_memory_binary-0.3.7.post2-cp312-cp312-win_amd64.whl
gllm_memory_binary-0.3.7.post2-cp312-cp312-manylinux_2_31_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.31+ x86-64 Details for gllm_memory_binary-0.3.7.post2-cp312-cp312-manylinux_2_31_x86_64.whl
gllm_memory_binary-0.3.7.post2-cp312-cp312-macosx_13_0_arm64.whl CPython 3.12 CPython 3.12 macOS 13.0+ ARM64 Details for gllm_memory_binary-0.3.7.post2-cp312-cp312-macosx_13_0_arm64.whl
gllm_memory_binary-0.3.7.post2-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for gllm_memory_binary-0.3.7.post2-cp311-cp311-win_amd64.whl
gllm_memory_binary-0.3.7.post2-cp311-cp311-manylinux_2_31_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.31+ x86-64 Details for gllm_memory_binary-0.3.7.post2-cp311-cp311-manylinux_2_31_x86_64.whl
gllm_memory_binary-0.3.7.post2-cp311-cp311-macosx_13_0_arm64.whl CPython 3.11 CPython 3.11 macOS 13.0+ ARM64 Details for gllm_memory_binary-0.3.7.post2-cp311-cp311-macosx_13_0_arm64.whl

Total release size: 21.0 MB

Release files / gllm_memory_binary-0.3.7.post2-cp313-cp313-win_amd64.whl

Incomplete provenance

This file belongs to a release with incomplete provenance: while this file has provenance metadata, other files in this release do not.

We recommend further investigation before installing this file. View details.

Download URL gllm_memory_binary-0.3.7.post2-cp313-cp313-win_amd64.whl
Size 1.9 MB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
e1afff550d7dfa869515108e279110ffaceea4bbe4f22a8b3b46002b3a3c3e39
BLAKE2b-256 checksum
How to use checksums
45d7922477a978746e6ef2e87077a21142750b8442b28b673ea28c7b6d592b30
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 log

Release files / gllm_memory_binary-0.3.7.post2-cp313-cp313-manylinux_2_31_x86_64.whl

Incomplete provenance

This file belongs to a release with incomplete provenance: while other files in this release have provenance metadata, this file does not.

We recommend further investigation before installing this file. View details.

Download URL gllm_memory_binary-0.3.7.post2-cp313-cp313-manylinux_2_31_x86_64.whl
Size 2.9 MB
Tags CPython 3.13 Linux glibc 2.31+ x86-64
SHA-256 checksum
How to use checksums
4678a10bf40567c2d4fd15fad005b073de8804b624e4b7914ce67df7963365a7
BLAKE2b-256 checksum
How to use checksums
d40b775aba48c7d928f9f0fb7c7993b3cf5e0596586e330434fc981083268e26
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"11","id":"bullseye","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / gllm_memory_binary-0.3.7.post2-cp313-cp313-macosx_13_0_arm64.whl

Incomplete provenance

This file belongs to a release with incomplete provenance: while this file has provenance metadata, other files in this release do not.

We recommend further investigation before installing this file. View details.

Download URL gllm_memory_binary-0.3.7.post2-cp313-cp313-macosx_13_0_arm64.whl
Size 2.4 MB
Tags CPython 3.13 macOS 13.0+ ARM64
SHA-256 checksum
How to use checksums
c4e90530b36b4c9f31f83c4ea8e7e64f3a63ceba7d95618d67becc894e155493
BLAKE2b-256 checksum
How to use checksums
410b52177c91aba9093a5dd1a59f0cdca80fe0219fef0ab8922a669a6c3f97f6
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 log

Release files / gllm_memory_binary-0.3.7.post2-cp312-cp312-win_amd64.whl

Incomplete provenance

This file belongs to a release with incomplete provenance: while this file has provenance metadata, other files in this release do not.

We recommend further investigation before installing this file. View details.

Download URL gllm_memory_binary-0.3.7.post2-cp312-cp312-win_amd64.whl
Size 1.9 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
10918044592d78289611fbaab061dd2db1b01528b92c6dba46e6e92f61600624
BLAKE2b-256 checksum
How to use checksums
83adf2d93f0262aa2996d2fce2b1e5c59b7dad764f706e46543a08de746451d7
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 log

Release files / gllm_memory_binary-0.3.7.post2-cp312-cp312-manylinux_2_31_x86_64.whl

Incomplete provenance

This file belongs to a release with incomplete provenance: while other files in this release have provenance metadata, this file does not.

We recommend further investigation before installing this file. View details.

Download URL gllm_memory_binary-0.3.7.post2-cp312-cp312-manylinux_2_31_x86_64.whl
Size 2.9 MB
Tags CPython 3.12 Linux glibc 2.31+ x86-64
SHA-256 checksum
How to use checksums
120e302331002918c6ef86cdeb54a5013426dd524293e28867ea901aad650f64
BLAKE2b-256 checksum
How to use checksums
e76e9cd2f4a4cab7e3273ffee078f3f8da56ada67b5fa1f70ee01dacaa6b4720
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"11","id":"bullseye","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / gllm_memory_binary-0.3.7.post2-cp312-cp312-macosx_13_0_arm64.whl

Incomplete provenance

This file belongs to a release with incomplete provenance: while this file has provenance metadata, other files in this release do not.

We recommend further investigation before installing this file. View details.

Download URL gllm_memory_binary-0.3.7.post2-cp312-cp312-macosx_13_0_arm64.whl
Size 2.3 MB
Tags CPython 3.12 macOS 13.0+ ARM64
SHA-256 checksum
How to use checksums
d60e3ff819901d7bd93206ed149e68cf931ce77354f691e61d6b2912695d4390
BLAKE2b-256 checksum
How to use checksums
7c9df1449e8524324432ad9d57c8d1320db100e2515b5cd25dd6131da14f6560
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 log

Release files / gllm_memory_binary-0.3.7.post2-cp311-cp311-win_amd64.whl

Incomplete provenance

This file belongs to a release with incomplete provenance: while this file has provenance metadata, other files in this release do not.

We recommend further investigation before installing this file. View details.

Download URL gllm_memory_binary-0.3.7.post2-cp311-cp311-win_amd64.whl
Size 1.9 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
4e3d895a3ea7baa187129f17964941d34e65be2d806854d9a0b1de4626b88c89
BLAKE2b-256 checksum
How to use checksums
e76d3403c76460d63ad19d10b3e4d43d918b7b086373d271cd951ab002b4ef9f
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 log

Release files / gllm_memory_binary-0.3.7.post2-cp311-cp311-manylinux_2_31_x86_64.whl

Incomplete provenance

This file belongs to a release with incomplete provenance: while other files in this release have provenance metadata, this file does not.

We recommend further investigation before installing this file. View details.

Download URL gllm_memory_binary-0.3.7.post2-cp311-cp311-manylinux_2_31_x86_64.whl
Size 2.6 MB
Tags CPython 3.11 Linux glibc 2.31+ x86-64
SHA-256 checksum
How to use checksums
82d44d9fcd2cb592b51a8a7f3c45f9e8cac9dd983d75292526d119db7b2f4fde
BLAKE2b-256 checksum
How to use checksums
ae63bd90ec89207940fbb1aa4e512175a63a56d10ae0883d7cd0d430a8c9e835
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"11","id":"bullseye","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / gllm_memory_binary-0.3.7.post2-cp311-cp311-macosx_13_0_arm64.whl

Incomplete provenance

This file belongs to a release with incomplete provenance: while this file has provenance metadata, other files in this release do not.

We recommend further investigation before installing this file. View details.

Download URL gllm_memory_binary-0.3.7.post2-cp311-cp311-macosx_13_0_arm64.whl
Size 2.3 MB
Tags CPython 3.11 macOS 13.0+ ARM64
SHA-256 checksum
How to use checksums
e22f92e39514c558e1cd828e4bc029369b33f32eccaa95f8fa31684ddf576750
BLAKE2b-256 checksum
How to use checksums
e9d1e708b79411afd25bd1b5623eaa9159528fba1d9b1e1dddb464707da5797e
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 log

Security for gllm-memory-binary 0.3.7.post2

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.

Incomplete provenance

3 of 9 release files were uploaded without provenance metadata.

Files with provenance 6 / 9
Files without provenance 3 / 9
Select from 9 files

Attestation for gllm_memory_binary-0.3.7.post2-cp313-cp313-win_amd64.whl

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 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.

Release history Release notifications | RSS feed

This release
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