jigkit
The shared foundations of small self-hosted web apps built on FastAPI, async SQLAlchemy and Svelte: settings, database, migrations, logging, health checks and test fixtures, each hardened once instead of copied between applications.
pip install "jigkit[db]"
| Module | Extra | What it gives an application |
|---|---|---|
jigkit.settings |
— | AppSettings: blank environment values mean unset, X or X_FILE for secrets (never both), a validated TZ, a data directory |
jigkit.db |
db |
an async engine with SQLite's pragmas (foreign keys, WAL, busy timeout), a session factory, a commit-or-roll-back session_scope |
jigkit.models |
db |
a declarative Base with deterministic constraint names, UtcDateTime, TimestampMixin |
jigkit.migrations |
db |
the whole of an Alembic env.py, with foreign keys off during SQLite table rebuilds and checked afterwards |
jigkit.logging |
— | stream and rotating file handlers, a level that changes at runtime, credential-carrying HTTP client loggers kept quiet |
jigkit.healthcheck |
— | python -m jigkit.healthcheck URL --expect database=connected, a container health probe |
jigkit.secrets |
— | load_or_create_secret, a generated secret kept owner-only in the data directory |
jigkit.sinks |
— | Point (timestamp with an explicit precision), Outcome, the Sink protocol, the neutral spooled form |
jigkit.spool, jigkit.delivery |
— | a bounded on-disk queue per destination, and write-now-or-spool-and-replay |
jigkit.influx |
influx |
InfluxDB 3 and 2.x sinks: line protocol in each batch's precision, and SQL reads from InfluxDB 3 |
jigkit.heartbeat |
heartbeat |
a push-monitor heartbeat after delivered writes, at most once per interval |
jigkit.web |
web |
FastAPI building blocks: write guard, security headers, SPA serving, health router, PWA manifest, serve() |
jigkit.scheduler |
— | TickLoop: in-process work on a fixed tick |
jigkit.notify |
notify |
Apprise delivery off the event loop, and URL redaction for logs |
jigkit.ratelimit |
— | RateLimiter: a token bucket per client with bounded memory |
jigkit.testing |
testing |
a pytest plugin (data_dir, no_network), migration checks run through the application's own env.py, and a recording stand-in HTTP server |
PostgreSQL is supported through the postgres extra. Python 3.14 or newer.
See the repository for the changelog and documentation.
1 maintainer
Metadata
1 maintainer
Release files for jigkit 0.3.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 |
|---|---|---|---|---|
| jigkit-0.3.0.tar.gz | 66.9 kB | With provenance | Details for jigkit-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jigkit-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for jigkit-0.3.0-py3-none-any.whl |
Total release size: 117.1 kB
Release files / jigkit-0.3.0.tar.gz
| Download URL | jigkit-0.3.0.tar.gz |
|---|---|
| Size | 66.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f2b169af8e5db2aa7ba45a32b14682f383e54f392248c31c08ea4c502158ecd
|
|
BLAKE2b-256 checksum How to use checksums |
bcec038ac5bca8ff1b7551d8c70b693796c935a6957ffa92edc5fab7d5afb84d
|
| 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 2, 2026.
Transparency logRelease files / jigkit-0.3.0-py3-none-any.whl
| Download URL | jigkit-0.3.0-py3-none-any.whl |
|---|---|
| Size | 50.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63da788d08b9f193798b2f03a13d82e0cc7ee694d0c7d1091ee075e1049aaeb3
|
|
BLAKE2b-256 checksum How to use checksums |
47cb81d34ec26037782c56f3182f238655a35bcb18e4f99695ec5d8a08fe833a
|
| 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 2, 2026.
Transparency logSecurity for jigkit 0.3.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for jigkit-0.3.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 2, 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.
