DEVSECOPS / TOOLING · 2025–2026

ScriptCCode under the microscope.

A local static analysis orchestrator. Multiple audit engines, one tool for the team.

Code analysis toolInternal tooling development
Node.jsTypeScriptReactElectron
ScriptC page on Open VSX showing the extension description, version 0.0.5 and MIT license
ScriptC published as an extension on Open VSX (screenshot from March 2026).

VERIFIABLE EVIDENCE · OCTOBER 2026

Downloads on Open VSX
726 ↗
Published version
0.0.5 · MIT license ↗
Source code
GitHub ↗
01 / CONTEXT

The problem

Reviewing quality and security with disconnected tools makes consistent standards difficult.

02 / IMPLEMENTATION

My contribution

Concurrent orchestration of SAST engines in isolated environments and an interface to bring their results together.

How it works

  1. Repository
  2. Isolated engines
  3. Concurrent analysis
  4. Unified report
03 / RESULT AND SCOPE

Code analysis tool

A workflow that gathers technical review findings and makes bugs and technical debt easier to track.

The portfolio demo shows a prepared report; it does not analyze repositories or represent a real security audit.

Design decisions

  • Consolidate results so code review is easier to follow.
  • Keep analysis separate from the reporting interface.
RELATED SERVICES

I can build something like this for you

Facing a similar problem?

We can talk through how you work today, define the scope and find a starting point.

Tell me your idea ↗