{
 "schema_version": 1,
 "generated": "2026-10-24",
 "id": "mah3sec-forgeguardian--write-custom-detection-signature",
 "repo": "Mah3Sec/ForgeGuardian",
 "repo_url": "https://github.com/Mah3Sec/ForgeGuardian",
 "repo_slug": "mah3sec-forgeguardian",
 "title": "Write a detection signature for an internal risk",
 "page_title": "How to write a detection signature for an internal risk with Forge Guardian",
 "summary": "Use the guided intel wizard to add a signature for a package or pattern your team wants blocked.",
 "who": "A security engineer who has seen a malicious package or pattern and wants the scanner to catch it without writing Go code.",
 "problem": "Community signatures may not cover a package or pattern that matters to your organization.",
 "outcome": "A validated, tested signature that the scanner applies to future scans.",
 "steps": [
  "Run `fgctl intel new` and follow the guided wizard, which the README says takes about 10 minutes",
  "Run `fgctl intel validate .` to check the signature schema",
  "Run `fgctl intel test .` against a real package to confirm the signature matches",
  "Run `fgctl scan .` on a project that includes the target to confirm the finding appears"
 ],
 "agent_prompt": "In the repo Mah3Sec/ForgeGuardian, create a detection signature for <package-or-pattern> using `fgctl intel new`, then run `fgctl intel validate .` and `fgctl intel test .`. Expected output is a passing validation and a test result for the target. Verify that validation passes before testing.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "The README says a signature needs no Go knowledge, but it does not describe the signature schema, so the wizard's prompts are the source of truth.",
 "category": "Security and science",
 "tags": [
  "Security and science"
 ],
 "lang": "go",
 "requirements": [
  "A terminal (bash on Linux or macOS, or PowerShell on Windows), or Docker",
  "A project directory with dependencies to scan",
  "Git and make only if building from source"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.7,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/mah3sec-forgeguardian/write-custom-detection-signature/",
 "md": "https://dedupedai.com/use-cases/mah3sec-forgeguardian/write-custom-detection-signature/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/mah3sec-forgeguardian--write-custom-detection-signature.json",
 "api_version": "v1"
}