D4rkninja Code Guardian
d4rkninja-code-guardian is a Claude Code plugin bundle for the Ship phase that combines supply-chain vulnerability scanning, API flow testing, and team coding memory across three security- and testing-focused plugins.
by d4rkNinja · github.com/d4rkNinja/code-guardian
Install when you want Claude Code to audit dependencies, probe APIs, and retain team coding memory across security-heavy shipping workflows.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install d4rkninja-code-guardian@d4rkNinja/code-guardianBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:d4rkNinja/code-guardian") and the paste-ready config with skillselion.get_install_config("plugin:d4rkNinja/code-guardian").
What it does
d4rkninja-code-guardian is a three-plugin Claude Code bundle from d4rkNinja/code-guardian aimed at indie builders who ship APIs and Node backends and cannot afford silent supply-chain or contract regressions. It combines security-oriented dependency and CVE/OSV scanning with automated API and flow testing, assertion helpers, and hooks that tie HTTP, Redis, and session behavior into reviewable traces. A coding-memory layer supports canonical team and user notes so probes, audits, and test failures stay linked to the same codebase context. Use it while integrating backends in Build and again in Ship when you need dependency audits, security probes, and PR-linked checks before release. It is an agent plugin bundle, not a hosted scanner service—you run it inside Claude Code on repos you control.
Highlights
- Three-plugin bundle spanning supply-chain scanning, automated testing, and coding-memory workflows.
- CVE and OSV vulnerability scanning with dependency inspection across multiple package ecosystems.
- HTTP REST flow-testing with assertions, API probes, and optional Redis-backed session hooks.
- Security probes, PR-linked autofix paths, and trace visualization for reviewing agent-driven changes.
- Canonical team/user memory weave for operating notes and promotion across collaborative repos.
Why builders use it
Agent-assisted shipping often skips systematic dependency audits, repeatable API assertions, and shared memory of what was already probed or fixed.
After install, Claude Code can run OSV/CVE-aware scans, structured HTTP flow tests with assertions, and session-linked security probes while preserving canonical team notes for the same repo.
At a glance
- Type - Plugin in Security.
- Adoption - 0 installs, 5 stars, 0 votes.
FAQ
Who is d4rkninja-code-guardian for?
It is for indie and small-team builders using Claude Code on backends who care about dependency risk, API contracts, and traceable security checks before merge.
When should I use d4rkninja-code-guardian?
Use it when integrating HTTP/Redis services and again before release to scan packages, run flow assertions, and attach PR-linked security probes.
How do I add d4rkninja-code-guardian to my agent?
Register the d4rkNinja/code-guardian plugin bundle in Claude Code from the repo marketplace entry, enable all three plugins, then point sessions at the target monorepo with your package manager and test runner available.
Comments
Share how you use d4rkninja-code-guardian, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.