Brimp Python binding
Brimp exposes a synchronous, Requests-style API backed by the shared native browser runtime. It runs in-process and does not start a CDP server.
import brimp
response = brimp.get("https://example.com")
print(response.status_code)
print(response.text) # original HTTP response
print(response.html) # DOM after JavaScript
Persistent cookies, connection reuse, JavaScript evaluation, and screenshots are available through a context-managed Session:
with brimp.Session() as session:
response = session.get("https://example.com", timeout=30)
response.raise_for_status()
print(session.evaluate("document.title"))
session.screenshot("page.png", full_page=True)
Private test and enterprise roots can be trusted without disabling certificate or hostname verification:
with brimp.Session(ca_bundle="path/to/cacert.pem") as session:
response = session.get("https://internal.example")
Persona JSON uses the versioned schema in ../../persona/:
persona_json = open("persona/example.json").read()
with brimp.Session(persona_json=persona_json) as session:
print(session.get("https://example.com").status_code)
See SUPPORT.md for the exact tested surface.
Binary wheels
The release workflow produces self-contained CPython 3.10+ ABI3 wheels for:
- manylinux 2.28 x86-64 and ARM64;
- macOS 11 or newer on Apple silicon; and
- Windows x86-64.
Run the Python wheels workflow manually to exercise all builds without
publishing. Pushing a v<project-version> tag publishes the validated four-wheel
set through the pypi environment and PyPI Trusted Publishing. Source
distributions are intentionally omitted because their native dependency build
is not self-contained.
1 maintainer
Metadata
1 maintainer
Release files for brimp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| brimp-0.1.1-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details for brimp-0.1.1-cp310-abi3-win_amd64.whl |
| brimp-0.1.1-cp310-abi3-manylinux_2_28_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.28+ x86-64 | Details for brimp-0.1.1-cp310-abi3-manylinux_2_28_x86_64.whl |
| brimp-0.1.1-cp310-abi3-manylinux_2_28_aarch64.whl | CPython 3.10 | abi3 | Linux glibc 2.28+ ARM64 | Details for brimp-0.1.1-cp310-abi3-manylinux_2_28_aarch64.whl |
| brimp-0.1.1-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details for brimp-0.1.1-cp310-abi3-macosx_11_0_arm64.whl |
Total release size: 209.9 MB
Release files / brimp-0.1.1-cp310-abi3-win_amd64.whl
| Download URL | brimp-0.1.1-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 49.1 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
fa7e6020b8a45bd8db78573beeb5f0dabe9557698b011324b9fd7786ca6e951a
|
|
BLAKE2b-256 checksum How to use checksums |
a661132abe653a2182a3c8ca6ac2d225b71354d661b09ad7f6af0fbce49691da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 27, 2026.
Transparency logRelease files / brimp-0.1.1-cp310-abi3-manylinux_2_28_x86_64.whl
| Download URL | brimp-0.1.1-cp310-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 64.1 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
7ad5f2634e8f880608ca3d7b20e4154f488eb87d3aac80d4a15eaa32db865f30
|
|
BLAKE2b-256 checksum How to use checksums |
4d685e20cee101cd8575372701f2a4366340d7130430897631ab0acec2194c9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 27, 2026.
Transparency logRelease files / brimp-0.1.1-cp310-abi3-manylinux_2_28_aarch64.whl
| Download URL | brimp-0.1.1-cp310-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 62.9 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
034a15185fda75c7353da4526df0e4176f8f9822d28f2d290eecf3b8ca36cbc6
|
|
BLAKE2b-256 checksum How to use checksums |
f5ad1f3171ec059b92f31c8630754f80bd7cb1ceae1997167018c074b251acee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 27, 2026.
Transparency logRelease files / brimp-0.1.1-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | brimp-0.1.1-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 33.9 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0ac732af3184ddf412fa0280bbdaa3a4c4bb0f8ba59dea7ff19ae9b55ee5c54c
|
|
BLAKE2b-256 checksum How to use checksums |
423c05df004292ef6848f78cbee43b62d3091cccf59df4742fb65da601d3e627
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 27, 2026.
Transparency logSecurity for brimp 0.1.1
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 4 files in this release have been uploaded with provenance metadata.
Attestation for brimp-0.1.1-cp310-abi3-win_amd64.whl
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 27, 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.
