feat: add llama-index-callbacks-hdp and hdp-llamaindex packages#22
Merged
asiridalugoda merged 2 commits intomainfrom Apr 8, 2026
Merged
feat: add llama-index-callbacks-hdp and hdp-llamaindex packages#22asiridalugoda merged 2 commits intomainfrom
asiridalugoda merged 2 commits intomainfrom
Conversation
asiridalugoda
force-pushed
the
feat/llamaindex-integration
branch
from
f280894 to
e1a65b3
Compare
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Three-layer integration providing cryptographic authorization provenance for LlamaIndex agents and RAG pipelines: - Layer 1: HdpInstrumentationHandler — modern dispatcher integration (LlamaIndex >=0.10.20), hooks QueryStartEvent, AgentToolCallEvent, LLMChatStartEvent, QueryEndEvent via root dispatcher - Layer 2: HdpCallbackHandler — legacy CallbackManager integration, hooks start_trace, end_trace, on_event_start/end for all FUNCTION_CALL and LLM events - Layer 3: HdpNodePostprocessor — inline retrieval hop recording and data classification enforcement in the RAG pipeline Shared ContextVar session state isolates tokens across concurrent async tasks. All crypto primitives bundled inline (Ed25519 + RFC 8785 JCS), consistent with all other HDP Python packages. hdp-llamaindex is a thin metapackage re-exporting from the llama_index namespace for users who discover HDP first. 43 tests passing across session isolation, chain verification, callback handler, and postprocessor.
…dp-llamaindex - CI: adds test matrix jobs (Python 3.10/3.11/3.12) for both packages - Release: adds tag-triggered test → vet (ReleaseGuard) → PyPI publish pipelines for python/llama-index-callbacks-hdp/v* and python/hdp-llamaindex/v* - Adds .releaseguard.yml to both packages (matches existing policy) Two GitHub PyPI environments required before release tags can fire: pypi-llama-index-callbacks-hdp pypi-hdp-llamaindex
asiridalugoda
force-pushed
the
feat/llamaindex-integration
branch
from
09c95bb to
8721224
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
llama-index-callbacks-hdp— three-layer HDP integration for LlamaIndex following the LlamaHub implicit namespace convention (from llama_index.callbacks.hdp import ...)hdp-llamaindex— thin metapackage re-exporting for users who discover HDP first (pip install hdp-llamaindex)Integration layers
Layer 1 — Modern instrumentation dispatcher (
HdpInstrumentationHandler): hooksQueryStartEvent,AgentToolCallEvent,LLMChatStartEvent,QueryEndEventvia the root dispatcher. Recommended for LlamaIndex ≥0.10.20.Layer 2 — Legacy CallbackManager (
HdpCallbackHandler): hooksstart_trace,end_trace,on_event_start/end. Drop-in viaSettings.callback_manager.Layer 3 — Node postprocessor (
HdpNodePostprocessor): records retrieval as a signed hop and optionally enforcesdata_classificationscope against node metadata. Used inline in RAG pipelines.All three layers share a
ContextVarfor token state — asyncio-safe, no cross-request leakage.Test Plan
verify_chain()confirms tamper-evident chain integrity end-to-end