Vinyasar: Policy-Driven Self-Healing Supervision for Yasarda
Policy-driven, evidence-bound self-healing supervision and mutation engine.
Installation
pip install vinyasar
# with optional YAML profile support:
pip install "vinyasar[yaml]"
Note on Package Overlap:
vinyasar0.4.1 embeds a bundledyasardanamespace reporting version 0.4.0. Users do not need to install both packages.
Public Feature Coverage
Vinyasar provides four primary console scripts:
vinyasar: The primary self-healing controller CLI.vinyasar-mcp: The MCP server for Vinyasar.yasarda: The embedded Yasarda engine CLI for low-level structural mutation.yasarda-mcp: The MCP server for Yasarda.
It also provides two subcommands under vinyasar for configuration hygiene and host verification:
vinyasar schema: Outputs the JSON schema for validation ofvinyasar.json/vinyasar.yamlprofiles.vinyasar doctor: Verifies the health and presence of the required environment and evaluator constraints.
Basic Example
# Validate your profile against the schema
vinyasar schema > profile.schema.json
# Check environment constraints
vinyasar doctor
# Run self-healing supervision in a target repository
vinyasar run /path/to/repo --profile vinyasar.json
Architecture
Vinyasar acts as an externally scheduled, trigger-driven reconciler. Schedule expressions (such as crons) are owned by external schedulers (e.g., launchd, systemd, or CI pipelines). When invoked, Vinyasar operates as a bounded one-shot process to inspect the target repository, consult the Yasarda engine, execute allowed playbooks, and exit, leaving behind a cryptographic-like ledger of actions taken.
Evaluator Prerequisite
For optional policy braking and advisory evaluations during operation, Vinyasar delegates to the jev evaluator. If these features are utilized, it requires jev >=0.6.2,<0.7.0 to be available on the host PATH.
Metadata
Release files for vinyasar 0.4.1
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 | Actions |
|---|---|---|---|---|
| vinyasar-0.4.1.tar.gz | 99.8 kB | Without provenance | Details for vinyasar-0.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vinyasar-0.4.1-py3-none-any.whl | Python 3 | none | any | Details for vinyasar-0.4.1-py3-none-any.whl |
Total release size: 182.7 kB
Release files / vinyasar-0.4.1.tar.gz
| Download URL | vinyasar-0.4.1.tar.gz |
|---|---|
| Size | 99.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e328f4cbe31f26edd9c41eb4da731133c4dea09b58ed9759597ba13a979b738
|
|
BLAKE2b-256 checksum How to use checksums |
49cbc6cd658a8f0ae91df51bb370fd7f0491b5ba71a03c92e4c5d842a5293b2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.11
|
Release files / vinyasar-0.4.1-py3-none-any.whl
| Download URL | vinyasar-0.4.1-py3-none-any.whl |
|---|---|
| Size | 82.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dbb4dc30942fd4aa1a5b4a7a6891246ccd0df9bd2afa06400b21b8acb8e06966
|
|
BLAKE2b-256 checksum How to use checksums |
60377c2f495f937ad65fdc95e93bcde567967a9bcd3b81731d5fc095aa47e196
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.11
|
Security for vinyasar 0.4.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.