little-bank
Little Bank is a framework for analyzing financial transactions.
Design goals
- All analysis should be a matter of summarizing credit, debit or balance of an account in a system. The intention is to reduce bugs by making all analysis use the same numerical implementation.
- This means that we're of the opinion that implementing filters and doing arithmetic on transactions outside of little-bank code is wrong. If we find ourselves grasping to do this, what we should instead do is introduce new accounts our possibly restructure the flow between the existing ones.
- Allow defining rules for a system in a declarative way.
- Disallow mutation. The design encourages immutable, append-only transactions.
- All operations that update the system are very similar: appending transactions which automatically verifies all defined rules, and persisting the new transactions. This allows centralizing code that saves transactions to a single place.
Non-goals
- Performance. This library is intended to be used to analyze systems of a small number of transactions. Therefor exposing APIs that are easy to reason about is a much higher priority than performance.
Metadata
Release files for little-bank 0.1.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 |
|---|---|---|---|---|
| little_bank-0.1.0.tar.gz | 6.4 kB | With provenance | Details for little_bank-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| little_bank-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for little_bank-0.1.0-py3-none-any.whl |
Total release size: 11.7 kB
Release files / little_bank-0.1.0.tar.gz
| Download URL | little_bank-0.1.0.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4eb76ddb7a69c840622ea1376b13f5c0b32d3cbd4ede815a9ced10dad974c267
|
|
BLAKE2b-256 checksum How to use checksums |
3bae6e3bd47bf8b7aa5505b5af348d0cb7cf1615435b5df60852ded9745d5f37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 May 21, 2025.
Transparency logRelease files / little_bank-0.1.0-py3-none-any.whl
| Download URL | little_bank-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f30a3c41d0a7edb270f95596b7b3b057b0a756860d17e93c3809b999b576d865
|
|
BLAKE2b-256 checksum How to use checksums |
b22909ed56521934d86a0b7952b9ab83c3c46834c4e62f019f2c4eb9257bbbac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 May 21, 2025.
Transparency logSecurity for little-bank 0.1.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 little_bank-0.1.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 May 21, 2025.
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.