audit_lockfile

2 registry entries were observed exposing a tool named audit_lockfile — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 12,342 of 40,590 scannable entries (30%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. import-guardian-mcpMCPcommunitytrust 60/100 · B
    v0.3.0
    ↓ 558/wk

    Catch AI-hallucinated (slopsquatted) npm imports in generated code BEFORE npm install. Scans a code block, flags imports of packages that don't exist on npm (the name an LLM invented and attackers register with malware) plus fresh lookalike squats. MCP se

    ClaudeCursorCopilotGemini
    import-guardianMIT3mo agonpmGitHubobserved · static extraction
    mcpmodel-context-protocolnpmsecuritysupply-chainslopsquatting
  2. lockfile-guardian-mcpMCPcommunitytrust 60/100 · B
    v0.1.0

    Audit a package-lock.json for supply-chain attacks BEFORE npm install. Cross-checks every resolved dependency against the live npm registry: blocks integrity (sha512) mismatches (lockfile poisoning) and not-on-registry entries, and flags new/fresh depende

    ClaudeCursorCopilotGemini
    lockfile-guardianMIT3mo agonpmGitHubobserved · static extraction
    mcpmodel-context-protocolnpmsecuritysupply-chainpackage-lock

All indexed toolsSearch the registry for audit_lockfile