veriq
[!WARNING] This project is in early development. The API may change in future releases.
veriq is a Python library for requirements verification and design calculation management in engineering projects. Think of it as a smart spreadsheet that tracks dependencies between calculations and automatically verifies that requirements are met.
What Does veriq Do?
When you define your engineering project with veriq, it:
- Organizes your design parameters - Define input data using Pydantic models
- Tracks calculation dependencies - Automatically resolves the order of calculations
- Verifies requirements - Checks that your design meets all specified requirements
- Exports results - Saves all inputs, calculations, and verification results to TOML files
Quick Example
Define your project in Python:
import veriq as vq
from pydantic import BaseModel
from typing import Annotated
project = vq.Project("MySatellite")
power = vq.Scope("Power")
project.add_scope(power)
@power.root_model()
class PowerModel(BaseModel):
battery_capacity: float # in Watt-hours
@power.verification()
def verify_capacity(
capacity: Annotated[float, vq.Ref("$.battery_capacity")],
) -> bool:
return capacity >= 100.0 # Minimum 100 Wh
Create an input file input.toml:
[Power.model]
battery_capacity = 150.0
Run verification:
veriq calc my_project.py -i input.toml -o output.toml --verify
Why Use veriq?
- Type Safety - Leverage Pydantic for validated, typed design parameters
- Dependency Tracking - Automatic resolution of calculation order
- Requirement Traceability - Link verifications to engineering requirements
- Reproducibility - TOML-based input/output for version control
License
MIT License
Acknowledgement
veriq originated in the shunichironomura/veriq repository, and its early development up to version v0.0.1 was supported by ArkEdge Space Inc.
1 maintainer
Metadata
1 maintainer
Release files for veriq 0.4.3
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 | |
|---|---|---|---|---|
| veriq-0.4.3.tar.gz | 77.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| veriq-0.4.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 173.2 kB
Release files / veriq-0.4.3.tar.gz
| Download URL | veriq-0.4.3.tar.gz |
|---|---|
| Size | 77.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0f9b9c4c39b3da8d03908cde4657a80a8a06a76bbfbf7043ba98ac9d52de38fc
|
|
BLAKE2b-256 checksum How to use checksums |
ee0f2950f642e527c73f8adeb6740d5ffa7e1f9c42b46c268a37a3a2d51a94ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 4, 2026.
Transparency logRelease files / veriq-0.4.3-py3-none-any.whl
| Download URL | veriq-0.4.3-py3-none-any.whl |
|---|---|
| Size | 96.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5d6c0b770fec7495bc7cbd3878a7bbce1e3df2f53115645de27fdeb4a2f636c1
|
|
BLAKE2b-256 checksum How to use checksums |
6b09e20bd3f58f481b75d6bcb48ebb2e95b559ad1761b03823a587e2fe7f0085
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 4, 2026.
Transparency logSecurity for veriq 0.4.3
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 veriq-0.4.3.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 Aug 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.
