Skip to content
View AyoubTadlaoui's full-sized avatar

Organizations

@forgeward

Block or report AyoubTadlaoui

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
AyoubTadlaoui/README.md
Atlas Kaisar

Listed in awesome-software-supply-chain-security (bureado PR #65, merged)   GoLogX listed in awesome-go (avelino PR #6389, merged)


I build the trust boundary for autonomous code. If you let an AI agent run npm install on its own, you need two things: a gate on what is allowed in, and a record of what it did that you cannot quietly edit afterward.

npmguard is the inbound gate. GoLogX is the outbound record. The same install-time gate is also being proposed upstream into the agents themselves. Single-binary, dependency-light, carried all the way to install.

Gate the install. Record the action.


❯ Forgeward, the security line

npmguard · Rust

An npm install firewall for AI coding agents. It scores every package against OSV malware data, typosquat and slopsquat heuristics, and install-script analysis, then returns a verdict before any lifecycle script runs. Works in Claude Code, Cursor, and Codex over MCP, or as a plain CLI.

Proof you can check: refuses real OSV malware (for example lodahs, MAL-2025-25502). Ships as one Rust binary, deliberately off npm and installed straight from source, so the gate cannot be poisoned by the registry it guards.

Rust MCP Release

GoLogX · Go

A tamper-evident audit core for Go. An append-only, hash-chained, optionally Ed25519-signed log/slog handler. If anyone edits, deletes, reorders, or forges a line, the offline logx verify command catches it and reports the first entry that was touched.

Proof you can check: zero external dependencies. The integrity code is built on the standard library alone (crypto/sha256, crypto/ed25519, crypto/rand), so the thing that proves your logs were not tampered with carries no third-party code in its own trust path.

Go MCP Zero deps Release


❯ Upstream

Merged (landed):

Proposed upstream (open, in review, not merged):

The same install-time gate, pushed into the agents themselves as a supply-chain inspector.

  • Continue: idea adopted by a maintainer and implemented in open PR #12727 (not yet merged, their commit). From open issue #12573.
  • OpenHands: SupplyChainSecurityAnalyzer, open issue #3560. Maintainers triaged it as an enhancement and pinged their security lead.
  • Cline: open issue #11340.
  • Crush: open issue #3090.
  • Goose: supply-chain typosquat inspector, PR #9642, closed by a maintainer who praised the work and asked for a smaller, design-aligned PR first.

❯ Also (personal, not the security line)

  • atlas-ragnarok: a terminal color theme plus a storm-fire GLSL shader, accepted into the Zed extension registry. Accepted into the Zed extension registry
  • GoFunAndChallenges: a hands-on Go course, runnable lessons and challenges, every package tested.


email github

footer

Pinned Loading

  1. GoLogX GoLogX Public

    Tamper-evident audit log for Go: an append-only, hash-chained, optionally Ed25519-signed log/slog handler, with offline logx verify. Built on the standard library, zero third-party dependencies. Al…

    Go 7

  2. npmguard npmguard Public

    npmguard secure AI agents auto-edits flows by screening every npm package for known-malicious code and typosquats before anything runs, in Claude Code, Cursor and Codex over MCP or the CLI. one Rus…

    Rust 2