08
Automated code auditin the Philippines
A review that happens once is out of date the week after it is delivered. Wiring the analysis into the build instead means every branch gets checked, the results arrive while the change is still fresh in someone's head, and nothing depends on remembering to run it.
What the work covers
- Static analysis running on every branch
- Checks wired into the build rather than run by hand
- Findings surfaced at review time, not after release
- Solidity static analysis for on-chain work
- Set up so it keeps running after we hand over
What it is built with
Slither
Solidity
Hardhat
Foundry
TypeScript
Docker
npm
Work in this area
SecurityPribado
Self-sovereign key manager. API keys sit in client-side encrypted vaults, proxied through a hardware enclave and rotated on a schedule.
Tech: Rust, WebAssembly, Hardware Enclaves, Encryption
Opens in a new tab
Web3StarBoarDB
A database that reads and writes to the chain itself, with no server in between.
Tech: Solidity, Web3.js, Smart Contracts, EVM
Opens in a new tab
Questions
- How is this different from a one-off security review?
- A review is a snapshot. This is the check that keeps running: it sits in the build and looks at every branch, so the code written after the review is covered too.
- Will it slow the team down?
- It runs on the branch, which is the cheapest place to find anything. The alternative is finding it in production, which is where fixes cost the most.
- Does it work on an existing repository?
- Yes. Wiring analysis into a build that already exists is the usual case, and it does not require rewriting what is there.
Other services
RFX Studios is a web development company in the Philippines. We build websites, mobile apps, backends and AI automations for growing brands, shipped in a week.