Integrations
Inside the tools you already use.
Keep your languages. Keep your data stack. Bracel executes critical behavior inside defined profiles, reports on the pull request and brings the evidence into your workspace.
01
GitHub
Where the check runs and where its verdict lands.
- Required
GitHub Actions
Where every check runs
The pull_request trigger on GitHub-hosted ubuntu-24.04 runners, in your own account. The action is pinned by full commit SHA.
- Required
Pull requests
Where the verdict appears
The check summary lands on the pull request: approved rule, why it ran, expected, observed, why, next step and provenance.
- Supported
Workflow artifacts
Optional evidence file
An opt-in JSON evidence file with the same fields as the summary, kept 7 days in your repository.
- Recommended
Code owners
Protects the rules
Protect .github/workflows/ and the rules file with CODEOWNERS, so changes to Bracel itself always get review.
- Supported
Branch protection
Optional merge gate
Bracel changes no merge settings. Your administrators decide whether the check is required.
02
Runtime and frameworks
The application profile validated end to end.
- Supported · defined profile
Node.js / TypeScript
Node.js 24 · Express 5 · TypeScript 7
JavaScript and TypeScript applications on Node.js 24 with Express 5, installed from package-lock.json. Approved business rules run through a pinned runtime, build and application profile.
- Supported · defined profile
Python
Python 3.13 · FastAPI · Uvicorn
Python 3.13 applications on FastAPI and Uvicorn, with hash-pinned requirements. Behaviour is verified through a versioned runtime, dependency and observation profile.
- Supported · defined profile
Java / JVM
Java 21 · Spring Boot 4.1 · Maven
Java 21 applications on Spring Boot 4.1, built with Maven against a checksum-verified dependency list.
- Supported · defined profile
Go
Go 1.26 · net/http
Go 1.26 services on the standard net/http library, built from go.mod and go.sum.
- Supported · defined profile
C# / .NET
.NET 10 · ASP.NET Core
.NET 10 applications on ASP.NET Core minimal APIs, restored from a locked packages file.
03
Data and services
Persisted state, transaction boundaries and defined Redis scenarios.
- Supported · defined profile
PostgreSQL
PostgreSQL 18
Persisted state, transaction boundaries, concurrent writes and recovery, across all five language profiles.
- Supported · defined profile
MySQL
MySQL 8.4
Business invariants against MySQL persistence and the transaction semantics declared by the profile, across all five language profiles.
- Supported · defined profile
Redis
Redis 8 · with PostgreSQL
The defined cache, session, deduplication and asynchronous side-effect scenarios, with PostgreSQL as the system of record. Redis use is declared per profile.
04
Packages and isolation
How the application is installed and contained.
- Supported · defined profile
npm
Node.js · package-lock.json
Installed with npm ci from package-lock.json, with install scripts disabled.
- Supported · defined profile
pip
Python · hash-pinned requirements.txt
Installed with --require-hashes from binary wheels only; every package must match its recorded hash.
- Supported · defined profile
Maven
Java · dependency checksum list
Resolved with strict checksums and compared with the repository’s dependency-checksums.txt, including on a cache hit.
- Supported · defined profile
Go modules
Go · go.mod and go.sum
Downloaded against go.sum and built read-only, so the module graph cannot change during the build.
- Supported · defined profile
NuGet
.NET · packages.lock.json
Restored in locked mode from packages.lock.json.
- Built in
Docker
Isolated execution
Images pinned by digest. Dependencies are fetched only while preparing, through a per-run proxy limited to the package registries; the application then runs with no network route out, a read-only file system and bounded memory, CPU and processes.
Explicit execution boundaries
Outside the profile, you get an answer. Never a silent pass.
An unsupported environment cannot establish PASS. Profiles define runtime versions, dependencies, persistence, observation and fault capabilities before verification starts.
Check your repository- Unlisted runtime and database versions
- Frameworks and protocols outside an admitted profile
- Unconfigured external services or production credentials
- CI systems outside the published installation contract
Product names and logos are trademarks of their owners. They are shown only to say that Bracel works with these products, not to imply endorsement or partnership.