palveron-crewai
PALVERON AI Governance adapter for CrewAI — task guardrails, step callbacks, and audit trails for every crew execution.
Add one guardrail function. Every task output gets checked against your PALVERON governance policies. PII is caught. Blocked outputs trigger retries. Everything gets an audit trail.
Installation
pip install palveron-crewai
Quick Start: Task Guardrail
from crewai import Agent, Task, Crew
from palveron_crewai import palveron_guardrail
# Create PALVERON guardrail
guardrail = palveron_guardrail(api_key="pv_live_xxx")
# Attach to any task
report_task = Task(
description="Write a customer analysis report",
expected_output="A report with customer insights",
agent=analyst_agent,
guardrail=guardrail, # ← PALVERON governance
guardrail_max_retries=2, # Retry if blocked
)
If the agent's output contains PII, secrets, or violates your policies, CrewAI automatically retries the task with PALVERON feedback.
Quick Start: Step Callback
from palveron_crewai import PalveronStepCallback
callback = PalveronStepCallback(api_key="pv_live_xxx")
crew = Crew(
agents=[researcher, writer],
tasks=[research_task, write_task],
step_callback=callback, # ← Every step governed
)
result = crew.kickoff(inputs={"topic": "AI Safety"})
# Governance summary
print(f"Checked: {callback.check_count}, Blocked: {callback.blocked_count}")
print(f"Traces: {callback.trace_ids}")
Combined Governance
from palveron_crewai import PalveronCrewGovernance
gov = PalveronCrewGovernance(api_key="pv_live_xxx")
task = Task(..., guardrail=gov.task_guardrail())
crew = Crew(..., step_callback=gov.step_callback())
result = crew.kickoff(inputs={...})
print(gov.summary()) # {"checks": 12, "blocked": 1, "trace_ids": [...]}
Configuration
guardrail = palveron_guardrail(
api_key="pv_live_xxx",
base_url="https://gateway.internal.corp:8080", # On-prem
fail_open=False, # Block on gateway errors (default)
metadata={"team": "ml"}, # Extra metadata on traces
)
How It Works
| Decision | Guardrail Behavior |
|---|---|
ALLOWED |
(True, output) — task proceeds |
MODIFIED |
(True, sanitized_output) — proceeds with PII redacted |
BLOCKED |
(False, feedback) — CrewAI retries with PALVERON feedback |
Links
License
Metadata
Release files for palveron-crewai 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| palveron_crewai-1.1.0.tar.gz | 7.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| palveron_crewai-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.0 kB
Release files / palveron_crewai-1.1.0.tar.gz
| Download URL | palveron_crewai-1.1.0.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2eeb6342a167b9a0ffac162c758175a83a228f24f764a53501bf52328a972629
|
|
BLAKE2b-256 checksum How to use checksums |
612ee8161fcfdbf30a7906b149984e12180fc14b671cc5bac10239c52e26ecad
|
| Upload date | |
|
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.
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 May 19, 2026.
Transparency logRelease files / palveron_crewai-1.1.0-py3-none-any.whl
| Download URL | palveron_crewai-1.1.0-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
81da3dabab067a0e10e9ffa2f130fe454fa71b42edb11b69af8ab1eeb65d58fd
|
|
BLAKE2b-256 checksum How to use checksums |
4d0c8e8e9294aca4e88663cd711468ce9569c66c6179a32a0213a153ded8edc0
|
| Upload date | |
|
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.
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 May 19, 2026.
Transparency log