Brinkpy CLI
Find the brink. Measure your distance. Stay back from it.
Brinkpy CLI is a Python command-line tool for reliability analysis, reliability-based design optimization, and simulation workflows using profile-based configuration.
It supports First-Order Reliability Method (FORM), Second-Order Reliability Method (SORM), Inverse FORM, Inverse SORM, Monte Carlo simulation, and Importance Sampling for rare-event probability estimation. Workflows cover forward reliability evaluation, reliability-constrained design, and post-design simulation with a consistent problem-module interface and support for correlated non-normal variables via Nataf transformation.
Run outputs are designed for engineering decisions and reporting, including reliability metrics and design points, tabulated summaries (Excel/JSON), plot reports (PDF), and pickled Matplotlib figure objects for post-processing.
What Brinkpy CLI Does
- Reliability analysis with FORM and SORM
- Reliability-based design with inverse FORM/SORM workflows
- Monte Carlo and importance sampling simulation
- Profile-based YAML configuration for repeatable runs
Install and Quick Start
On first use, Brinkpy will prompt you to authenticate. If you do not already have an account, you can create one during the sign-in flow.
# Install from PyPI
pip install brinkpy
# Show help
brinkpy --help
# Copy packaged example problems
brinkpy examples copy
# Run an analysis with the default profile
brinkpy analyze
Profile Management
Profiles are YAML files under profiles/ that control run options.
# Create and edit a custom profile
brinkpy profile new custom
brinkpy profile nano custom
# or
brinkpy profile vim custom
# Validate, list, copy, rename
brinkpy profile validate custom
brinkpy profile list
brinkpy profile copy default mycopy
brinkpy profile rename oldname newname
Full Documentation
Read the full documentation at:
Requirements
- Python 3.10+
- Internet connection for API access and authentication
Testing and Validation
Unit and integration tests are provided in the tests/ directory.
# Run unit tests
python -m unittest discover tests -p 'test_*.py' -v
# Run integration tests with real API calls
BRINKPY_RUN_API_TESTS=1 python -m unittest tests.test_cli_api_integration -v
See the testing guide for details on test structure and rate limit behavior.
Notes
- Auth0 device flow uses public values (domain, client ID, audience). No client secret is used in the CLI.
Metadata
Release files for brinkpy 0.2.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 |
|---|---|---|---|---|
| brinkpy-0.2.0.tar.gz | 38.6 kB | With provenance | Details for brinkpy-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| brinkpy-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for brinkpy-0.2.0-py3-none-any.whl |
Total release size: 92.0 kB
Release files / brinkpy-0.2.0.tar.gz
| Download URL | brinkpy-0.2.0.tar.gz |
|---|---|
| Size | 38.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5cfb02e1bbf5877dac300e0f76096ac2ead0168e89da6edaea2607e11afd59a8
|
|
BLAKE2b-256 checksum How to use checksums |
2a2372501a5a2ee7ce58577ecb28a3696a33c36c4f6cc0fdd8794725801ade22
|
| 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 / brinkpy-0.2.0-py3-none-any.whl
| Download URL | brinkpy-0.2.0-py3-none-any.whl |
|---|---|
| Size | 53.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8f453faeac9d94e9daca37841d8b2c1777982978cb3ac9079307062ae0788b86
|
|
BLAKE2b-256 checksum How to use checksums |
f91a5085b166fc3b845416a79e6b26be36bff24f1395d38c48e55a26ff4ce8dc
|
| 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 brinkpy 0.2.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 brinkpy-0.2.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.