BlueDot IT work
Proof, not a repository dump.
Two public engineering examples show the problem, the work, the artifact, and the result.
Security engineering
Security middleware
Security checks are often separated from the place where a developer is making the change. This TypeScript and Next.js middleware puts feedback back into that working context.
- Work
- Checks headers, CORS, and npm dependencies and reports findings through logs or a browser overlay.
- Evidence
- Public TypeScript repository with the checks and developer feedback path available for inspection.
- Result
- A class of application-security concerns becomes visible while the relevant code and context are still in front of the developer.
AI automation + security
GhostMCP
An agent that can call useful tools can also create side effects. Permission, approval, credential, and audit decisions need to be explicit.
- Work
- Policy-guarded tools, curated workflows, scheduling, dashboards, and audit logging for authorized assessments.
- Evidence
- Public beta repository documenting the server, tool controls, workflows, and audit trail.
- Result
- Tool authority and operator oversight are visible enough to review before an agent enters a real workflow.
Open source archive
The rest of the lab stays inspectable.
Additional public systems cover agent runtimes, model routing, vulnerability intelligence, and reproducible evaluation. They are useful technical evidence, but they do not represent private client outcomes.
Browse BlueDot IT on GitHub