Smart Contract Security Dashboard

Scans smart contract repositories on every push and mints a certificate recording the scan.

Role
Full-stack engineer · 5-person team
Period
Jan 2023 – Jul 2023
Stack
Next.js · NestJS · Solidity · Hardhat · IPFS · Prisma · PostgreSQL · Docker · Octokit
Runs on
Hosted service
Code

HvA team project with Byont Labs; the repository isn't public. Happy to walk through it in an interview.

At a glance

Problem
Smart contract developers need security feedback on every change, explained so that non-specialists can act on it.
My contribution
On a five-person team, I built the GitHub OAuth flows, the webhook-driven scan pipeline, the Prisma data model and the ERC-721 certificate integration.
Outcome
Every push runs Slither and Mythril in Docker, an LLM explains the findings, and an NFT certificate records that the scan ran.
Landing page of the smart contract security dashboard, headed 'Develop. Check. Ship.', with a Get Started button and the Mythril, Slither and OpenAI logos under 'The scanner that we use'.
fig. 1 · the dashboard's landing page

Context

A developer-facing dashboard that scans smart contract repositories for vulnerabilities and mints an NFT certificate recording a completed scan, built by a five-person team with Byont Labs in the HvA blockchain semester.

What I built

Built full-stack features spanning GitHub OAuth flows, webhook-driven scan pipelines, the Prisma data model, and the ERC-721 contract integration for on-chain certificates.

Architecture

  • GitHub OAuth + webhooks to trigger a scan on every push.
  • Dockerized Slither and Mythril analysis per repository.
  • Prisma/Postgres data model for users, repos, and scan outputs.
  • ERC-721 smart contract for scan certificates.

Execution

  • Built a Next.js dashboard with scan history and results views.
  • Implemented LLM summaries to translate raw findings into clear explanations.
  • Integrated IPFS for certificate metadata and retrieval.

Results

  • Reproducible security scans for every code change.
  • Plain-language explanations of each finding for non-specialists.
  • An on-chain record that a scan was completed. The certificate shows that the automated scanners ran, not that the contract is free of vulnerabilities.