dirigent-blocks
The built-in pack: one install that brings every block family dirigent ships -- base, http, storage, execute, sql, jq and queues -- and the outbound alert channels beside them.
The three channels here are webhook, slack and email, each with a connection kind of the
same id, so an alert is delivered through the one connection path every credential in this
instance goes through. The fourth channel, log, is dirigent-block-base's, because it needs
no credential.
A family is installable on its own: a worker that only runs jq needs
dirigent-block-jq and nothing else. This package is what an instance installs to have the lot.
1 maintainer
Metadata
1 maintainer
Release files for dirigent-blocks 0.36.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 | Provenance | Actions |
|---|---|---|---|---|
| dirigent_blocks-0.36.0.tar.gz | 9.1 kB | With provenance | Details for dirigent_blocks-0.36.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dirigent_blocks-0.36.0-py3-none-any.whl | Python 3 | none | any | Details for dirigent_blocks-0.36.0-py3-none-any.whl |
Total release size: 19.8 kB
Release files / dirigent_blocks-0.36.0.tar.gz
| Download URL | dirigent_blocks-0.36.0.tar.gz |
|---|---|
| Size | 9.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
395e7d142ca32184e8c6ccbb13daf492608b3753c6540a51f35638d5502c7cfa
|
|
BLAKE2b-256 checksum How to use checksums |
74e3cab10dc6a451fe63a685d595512f1957fe43f27bfd0ff3f9541790abc9fc
|
| 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 Nov 4, 2026.
Transparency logRelease files / dirigent_blocks-0.36.0-py3-none-any.whl
| Download URL | dirigent_blocks-0.36.0-py3-none-any.whl |
|---|---|
| Size | 10.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
882b51ccccca1fe744457517dcfc35e92962b209d7c58b1153ab646d8b793ed8
|
|
BLAKE2b-256 checksum How to use checksums |
8fc38ee67cf10ff6399159f4b89b178810422256017c916131bef8ec2dc22d5c
|
| 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 Nov 4, 2026.
Transparency logSecurity for dirigent-blocks 0.36.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for dirigent_blocks-0.36.0.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 Nov 4, 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.
