Finance Developer Assistant
Review committed changes, reproduce findings and inspect readiness evidence for finance software, using your chosen model or deterministic offline analysis.
Local-first, no telemetry. The default provider is offline. The demo and local
dashboard make no external requests. Remote model reviews and GitHub inspection
require explicit configuration and approval. The dashboard ships prebuilt and
binds only to 127.0.0.1; Node is needed only for frontend development.
What it does
- Review source: freeze commits, screen paths/content, inspect coverage and use configurable finance, research, quant or custom review profiles.
- Reproduce: run approved recipes on screened snapshots in a pinned, network-disabled container; trusted local execution requires explicit opt-in.
- Propose carefully: inspect and approve exact patch hashes, protect policy files and preserve guarded recovery copies. No automatic merge, deploy or trade.
- Track evidence: local spend reservations, usage, findings, readiness and a tamper-evident audit trail; unknown outcomes stay visible and block readiness.
- Configure locally: preview a diff, confirm a save, inspect statistics and run Health checks from the browser. API keys stay in environment variables.
Start in one minute
Python 3.11+ is required; Git is needed for source workflows. After the first PyPI
release is published, install with pip or pipx.
The distribution is finledgerpoli; the command and import package remain
finassist, with finledgerpoli also available as a command alias.
pip install finledgerpoli
# Alternatively, use an isolated command environment:
pipx install finledgerpoli
finassist demo
finassist doctor
finassist init --output finassist.json
finassist --config finassist.json dashboard
Until publication, or to develop from source, clone and install instead:
git clone https://github.com/EleutheroiEdge/finance-dev-assistant.git
cd finance-dev-assistant
python3 -m venv .venv
.venv/bin/python -m pip install .
.venv/bin/finassist demo
.venv/bin/finassist init --output finassist.json
.venv/bin/finassist --config finassist.json dashboard
On Windows PowerShell, use py -3 -m venv .venv, then
.\.venv\Scripts\python.exe -m pip install . and
.\.venv\Scripts\finassist.exe demo. No activation or execution-policy change
is required. macOS/Linux use the commands above. See platform setup
for UTF-8, permissions, Git modes and Docker Desktop details.
The demo uses fictional finance checks and needs no key, model download or
container. It demonstrates deterministic oracles, not model review quality.
Download the short terminal recording and play it locally
with asciinema play docs/images/demo.cast.txt; no hosting account is needed.
Dashboard preview
These screenshots come from an isolated synthetic fixture. All displayed spend, tokens, findings and review activity are fictional; no provider was called.
Statistics and Health screenshots
See the dashboard guide for configuration previews, explicit confirmation, audit statistics and same-user security limits.
Review your first change
After inspecting your configuration and source policy:
finassist --config finassist.json plan --repo . --base main --head HEAD \
--output .finassist/context.json
finassist --config finassist.json review --packet .finassist/context.json \
--output .finassist/offline-review.json
Offline analysis does not claim a model review or test execution. To use a remote model, choose its provider/model/endpoint, price assumptions and named environment variable; enable network access deliberately and approve the exact outgoing packet. There is no automatic provider fallback. Provider setup explains OpenAI Responses, Anthropic, Gemini, compatible Chat Completions and local Ollama. Compatibility tests use fake transports; not every model/service is live-tested.
Guides
| Goal | Guide |
|---|---|
| Adapt to your own team | Fork and customize |
| Understand protection and limits | Threat model, security policy |
| Configure profiles, paths and budgets | All configuration options, examples |
| Automate command results | Exit codes and JSON contracts |
| Plan, review, check and recover | Workflow contracts, auditing/readiness |
| Evaluate findings or manage evidence | Evaluation, research inputs |
| Integrate your coding agent | Portable templates, evidence-review skill |
| Maintain and release a fork | Repository settings, releasing |
Keep .finassist/ and private artifacts out of Git. Inspect every outgoing packet:
content screening cannot prove confidentiality. A readiness result grants no merge,
deployment or financial authority. Local audit hashes cannot defeat a malicious
same-user rewrite; budget estimates are not provider-enforced billing caps.
Contribute
python -m pip install -r requirements-dev.lock
python -m pip install --no-deps --no-build-isolation -e .
python -m pytest -q
ruff check src tests scripts
finassist demo
finassist scan --repo .
Use synthetic fixtures and fake provider transports. See contributing, architecture and media reproduction. Scorecard is a posture indicator, not certification; results appear after its workflow publishes. The PyPI badge will be added after the owner verifies the first public release. Forks must update badge/repository links and maintainer settings.
MIT licensed. See LICENSE.
Metadata
Release files for finledgerpoli 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 |
|---|---|---|---|---|
| finledgerpoli-0.3.0.tar.gz | 582.4 kB | With provenance | Details for finledgerpoli-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| finledgerpoli-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for finledgerpoli-0.3.0-py3-none-any.whl |
Total release size: 779.9 kB
Release files / finledgerpoli-0.3.0.tar.gz
| Download URL | finledgerpoli-0.3.0.tar.gz |
|---|---|
| Size | 582.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
be75e1751e2be07141cd7f76cb2c90e159b26467539c568ff4622106e694e117
|
|
BLAKE2b-256 checksum How to use checksums |
71fd9042c348acd2ddd43383bc243738f6b817d3389b88f2d7f2b280681ab1b9
|
| 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 Oct 28, 2026.
Transparency logRelease files / finledgerpoli-0.3.0-py3-none-any.whl
| Download URL | finledgerpoli-0.3.0-py3-none-any.whl |
|---|---|
| Size | 197.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7e0a483e5f973ab3d75052a2abfeceb6ab3d0b606d64f3a068d871d0f148eb40
|
|
BLAKE2b-256 checksum How to use checksums |
e14dfe60bb4f71332a6df9eaa5c68abb04602e96dce99162e961d2649a02df1e
|
| 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 Oct 28, 2026.
Transparency logSecurity for finledgerpoli 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 finledgerpoli-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 Oct 28, 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.