Supply Chain Security
7 posts tagged #supply-chain-security
7 posts on Supply Chain Security, spread across Dev Tools & AI Workflow (3), AI Security & Safety (2), LLM Hardware & Local AI (1) — most read: “How to Build a Local Model Registry for GGUF” and “How to Stop Repo Prompt Injection in Coding Agents”.
Developer Tools How to Build a Local Model Registry for GGUF
Stop downloading random weights from links. Build a local model registry with GGUF versioning, provenance attestations, eval gates, and a real rollback plan.
Cybersecurity How to Stop Repo Prompt Injection in Coding Agents
Repo-level prompt injection turns “clone and ask the agent” into a supply-chain compromise. Here’s the threat model, a safe demo, and practical mitigations.
Developer Tools Wayback Machine Alternatives: A Developer Archiving Playbook
Wayback Machine alternatives aren’t just other sites to “view old pages.” For developers, archiving is a supply-chain and ops problem: reproducible docs, mirrored release assets, checksums, and restore drills.
Developer Tools bun.lock vs bun.lockb: Bun Lockfile Threat Model + CI Checks
bun.lockb made Bun installs fast, but it also changed how you audit dependency drift. Here’s what’s inside, what integrity it gives you, and how to enforce it in CI.
Developer Tools Rust Reproducible Builds, SBOM and Signed Artifacts
A Rust release pipeline: pin toolchains, make builds reproducible, gate deps with cargo-vet, generate SBOM + SLSA provenance, and sign everything with keyless cosign.
Cybersecurity LLM Supply Chain Security Checklist: Lock Down Agents
A CI-ready checklist to treat models, MCP servers, tool plugins, and prompt packs as real dependencies. Pin, sign, attest, sandbox, and monitor before your agent ships malware.
![claude code terminal laptop screen — illustration for article on Claude Code Security [2026]: Risks, Safe](https://img.kunalganglani.com/images/vzekdneq/production/ae489a760c8efd343421ac3a5e4b1f9b048acc2c-1200x675.webp?auto=format&fit=max&q=75&w=600)
Technology Claude Code Security: Risks, Safe Setup, Team Policy
Claude Code is safe only if you treat it like a junior engineer with terminal access. Here’s the 2026 playbook: permissions, sandboxing, egress controls, MCP allowlists, retention settings, and incident response.
Keep exploring
Close to this topic, not on this page.
