curadise-agent
Async monitoring agent for Curadise - collects system metrics, sends heartbeats, and executes remote commands with security-first design.
Features
- Async-first architecture - Built on
anyiofor high-performance concurrent operations - System metrics collection - CPU, memory, disk, network via
psutil - HTTP health checks - Monitor endpoints with customizable checks
- Buffered transport - In-memory buffer with optional persistence for reliability
- Heartbeat service - Regular health reporting with automatic reconnection
- Remote command execution - Secure sandboxed execution with allowlist/denylist
- mTLS support - Mutual TLS authentication for secure communication
- JWT authentication - Token-based auth with automatic refresh
- Hot-reload configuration - Watch config files for changes without restart
- Structured logging - JSON logging via
structlogfor easy parsing - Auto-remediation - Server-driven playbooks with detection rules
- Detection checks - Command, HTTP, process, and log pattern monitoring
- Signed playbooks - ECDSA-SHA256 signature verification
- Rate limiting - Configurable cooldowns and max remediations per hour
- Dry-run mode - Test remediation without executing
Requirements
- Python 3.12+
- Linux or macOS
Installation
# Using pip
pip install curadise-agent
# Using uv (recommended)
uv pip install curadise-agent
# From source
git clone https://github.com/pysingh09/curadise-agent.git
cd curadise-agent
uv pip install -e .
Quick Start
- Create a configuration file:
cp examples/agent.yaml /etc/curadise/agent.yaml
- Set your enrollment token:
export CURADISE_ENROLLMENT_TOKEN="your-token-here"
- Run the agent:
curadise-agent run --config /etc/curadise/agent.yaml
CLI Commands
# Run the agent
curadise-agent run --config agent.yaml
# Check agent version
curadise-agent version
# Validate configuration
curadise-agent config validate --config agent.yaml
# Show effective configuration
curadise-agent config show --config agent.yaml
# Register agent with server
curadise-agent register --token <enrollment-token>
# Check agent status
curadise-agent status
# Unregister agent
curadise-agent unregister
Configuration
The agent is configured via YAML files with Jinja2 templating support for environment variables.
Minimal Configuration
server:
url: "https://curadise.example.com"
auth:
enrollment_token: "{{ env('CURADISE_ENROLLMENT_TOKEN') }}"
Key Configuration Sections
| Section | Description |
|---|---|
server |
Server URL, timeout, SSL settings |
auth |
Enrollment token, mTLS certificates |
buffer |
Memory buffer size, persistence, batching |
retry |
Retry attempts, backoff, circuit breaker |
heartbeat |
Heartbeat interval and health metrics |
collectors |
System metrics and HTTP check configuration |
executor |
Command execution settings and allowlist |
remediation |
Auto-remediation settings and playbook controls |
logging |
Log level, format, and file rotation |
state |
Persistent state directory |
tags |
Custom tags for metrics and heartbeats |
See examples/agent.yaml for a complete configuration reference.
Remediation Configuration
remediation:
enabled: false
sync_interval: 300.0
check_interval: 60.0
max_concurrent: 1
max_remediations_per_hour: 20
require_signature: true
dry_run: false
| Option | Default | Description |
|---|---|---|
enabled |
false |
Enable auto-remediation service |
sync_interval |
300.0 |
Seconds between playbook sync from server |
check_interval |
60.0 |
Seconds between detection rule checks |
max_concurrent |
1 |
Max concurrent remediation executions |
max_remediations_per_hour |
20 |
Rate limit for remediation actions |
require_signature |
true |
Require ECDSA-SHA256 signatures on playbooks |
dry_run |
false |
Log actions without executing |
Environment Variables
Configuration values can reference environment variables:
auth:
enrollment_token: "{{ env('CURADISE_ENROLLMENT_TOKEN') }}"
http_checks:
- url: "https://api.example.com/health"
headers:
Authorization: "Bearer {{ env('API_TOKEN') }}"
Architecture
curadise-agent/
├── src/curadise_agent/
│ ├── auth/ # JWT tokens, mTLS, registration
│ ├── collectors/ # Metrics collectors (system, HTTP)
│ ├── config/ # Configuration loading, schema, watcher
│ ├── executor/ # Command execution with sandbox
│ ├── heartbeat/ # Heartbeat service and health checks
│ ├── models/ # Pydantic models (domain, API)
│ ├── remediation/ # Auto-remediation with playbooks
│ ├── state/ # Persistent state management
│ ├── transport/ # HTTP client, buffering, batching
│ └── utils/ # Logging, retry, shutdown handling
└── tests/
├── unit/ # Unit tests
└── integration/ # Integration tests
Development
Setup
# Clone the repository
git clone https://github.com/pysingh09/curadise-agent.git
cd curadise-agent
# Create virtual environment
uv venv
source .venv/bin/activate
# Install with dev dependencies
uv pip install -e ".[dev]"
# Install pre-commit hooks
pre-commit install
Running Tests
# Run all tests
pytest
# Run with coverage
pytest --cov=curadise_agent --cov-report=html
# Run only unit tests
pytest tests/unit/
# Run integration tests
pytest tests/integration/ -m integration
Code Quality
# Linting
ruff check src/ tests/
# Type checking
mypy src/
# Format code
ruff format src/ tests/
Security
The agent implements defense-in-depth security:
Command Execution
- No shell injection - Uses
subprocess_exec, notsubprocess_shell - Character blocklist - Rejects dangerous shell metacharacters
- Executable allowlist - Only approved binaries can run
Network Security
- SSRF prevention - Blocks internal IPs (10.x, 172.16.x, 192.168.x, 127.x, 169.254.x)
- DNS rebinding protection - Validates resolved IPs before requests
- Scheme validation - Only HTTP/HTTPS allowed
File System Security
- Path traversal prevention - Uses
realpath()with symlink resolution - Allowed path prefixes - Files must be under configured directories
Cryptographic Security
- Playbook signatures - ECDSA-SHA256 verification required
- Nonce replay prevention - 24-hour expiration window
- JWT with refresh - Short-lived tokens with automatic refresh
General
- mTLS support - Mutual TLS for server authentication
- No secrets in config - Use environment variables for sensitive data
License
MIT License - see LICENSE file for details.
Metadata
Release files for curadise-agent 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| curadise_agent-0.1.3.tar.gz | 90.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| curadise_agent-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 191.1 kB
Release files / curadise_agent-0.1.3.tar.gz
| Download URL | curadise_agent-0.1.3.tar.gz |
|---|---|
| Size | 90.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
65959e89aa8aa1ca92ad448c6fdd8f8fd3c1c9b1d056e4e81293cb26ed405956
|
|
BLAKE2b-256 checksum How to use checksums |
d070c1cff973aebbc1e9d6d970efc2f1f023b357ae11b8cc6119a7bfa821cfd6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 23, 2026.
Transparency logRelease files / curadise_agent-0.1.3-py3-none-any.whl
| Download URL | curadise_agent-0.1.3-py3-none-any.whl |
|---|---|
| Size | 100.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
898e1c9bbcf8524eb0b11a84a4aea4b1fe123479e1bad242aa9734ef6f8cb671
|
|
BLAKE2b-256 checksum How to use checksums |
bd35eafcb2382a9ec831de85236055fd1464dc95ee603313d42ff8c3b05fa371
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 23, 2026.
Transparency logSecurity for curadise-agent 0.1.3
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 2 files in this release have been uploaded with provenance metadata.
Attestation for curadise_agent-0.1.3.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 Jan 23, 2026.
Transparency logA 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.