CanopiiCanopiiAll serversEnterprise →
io.github.jghiringhelli/codeseeker

io.github.jghiringhelli/codeseeker v2.1.2

Security Trust Score
Grade C · Needs review
Tier 1 · Public sourceHigh confidence · 98%
Declared MCP capabilities
Resources

Run it through Canopii Gateway — policy enforcement, audit trail, and per-user attribution on every call.

2 issues capping this score
  • mediumNo install/post-install scripts — runs postinstall
  • mediumNo over-broad / destructive tools — 1 over-broad tool(s)
Reputation20stars3forks1.7kdownloads/mo3open issues8d agolast commit1yage

Security controls

Deterministic, evidence-backed. Score earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

  • Fail
    User-in-the-Loop / Approval Scopeguard1 over-broad tool(s)

    No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval. How many servers fail this?

    System Architect

    Fix: Scope tools narrowly; avoid arbitrary command execution and destructive defaults.

  • Warn
    Strict JSON Schema Enforcementschemas not strict

    Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.

    Fix: Set additionalProperties:false and require explicit parameters on every tool.

  • Pass
    Indirect Prompt Injection (IPI) Defensesguardno injection markers

    Tool/prompt/resource text is free of hidden instructions that could hijack the agent.

  • Pass
    Tool Definition Integrityguardtool definitions stable; no risky changes in version history

    Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

  • Pass
    In-Session Definition Integrityguardno call-gated or call-time tool definition changes

    Tool and prompt definitions stay fixed during a session — they don't change after a few calls, which is how runtime-gated rug-pulls slip past one-time review.

Application Security Checks

  • Fail
    No install/post-install scriptsguardruns postinstall

    install hooks run arbitrary code on every consumer at install time. How many servers fail this?

    Fix: Remove preinstall/install/postinstall scripts, or document and minimize them.

  • Warn
    Dependencies pinned (lockfile)no lockfile found

    A lockfile makes installs reproducible and resistant to silent dependency swaps.

    Fix: Commit a lockfile (package-lock.json / pnpm-lock.yaml / poetry.lock).

  • Warn
    Published with provenanceno provenance attestation

    Build provenance attests the artifact was built from the claimed source by CI.

    Fix: Publish with npm provenance (--provenance) from a trusted CI.

  • Warn
    Established maintainersingle maintainer

    Brand-new / single anonymous maintainers raise takeover and malware risk.

    Fix: Publish under an established account/org; add multiple maintainers.

  • Warn
    Has a security policyno security policy

    A SECURITY.md gives a private path to report vulnerabilities.

    Fix: Add SECURITY.md with a disclosure contact and process.

  • Pass
    No command-injection sinksguardno sinks found

    Untrusted tool input reaching a shell yields remote code execution.

  • Pass
    No dynamic code executionguardno sinks found

    eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.

  • Pass
    No path traversalguardno sinks found

    Naive path checks let tools read/write outside intended directories (EscapeRoute-class).

  • Pass
    No SSRF sinksguardno sinks found

    Fetching tool-supplied URLs can pivot into internal networks and metadata services.

  • Pass
    No unsafe deserializationguardno sinks found

    pickle/yaml.load/etc. on untrusted data can execute code.

  • Pass
    No committed secretsguardno secrets found

    Hardcoded keys/tokens in published source are live credentials an attacker can use.

  • Pass
    Credentials sourced from environmentreads credentials from environment

    Reading secrets from env/secret stores avoids hardcoding them.

  • Pass
    No known-vulnerable dependencies1 runtime deps, no known CVEs

    Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.

  • Pass
    Package name not typosquattingguarddistinct package name

    Names mimicking popular packages are a common malware delivery vector.

  • Pass
    Actively maintainedrecent commits

    Unmaintained servers don't receive security fixes.

  • Pass
    Repository not archivedguardactive

    Archived repositories will never be patched.

  • Pass
    Declares a licenseApache-2.0

    A clear license is required for legal enterprise use.

  • Pass
    Adoption & popularityestablished adoption

    A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.

  • Not checked
    Signed releasesnot evaluated

    Signed releases let consumers verify artifacts weren't tampered with.

Transport & Trust Model

  • Warn
    Execution Sandboxingruns natively (no container image)

    A container/sandbox image limits blast radius; a server that runs natively has full host access.

    Fix: Ship a Dockerfile/Containerfile (or document a sandboxed run) so the server runs isolated.

  • Pass
    Network Exposureno bind-all detected

    Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.

  • N/A
    Transport Encryption (TLS)guardno remote endpoints

    Plaintext HTTP exposes traffic and bearer tokens to interception.

  • N/A
    IAM / Authentication Scopingno remote endpoints

    OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.

  • N/A
    No Token Passthroughguardno HTTP transport

    The client's token is never forwarded to downstream APIs — the server obtains its own, correctly-scoped credential instead.

  • N/A
    DNS-Rebinding Protectionno HTTP transport

    HTTP endpoints reject requests carrying an unlisted Origin, so a malicious web page can't drive the server through the user's browser.

  • N/A
    Live Endpoint Reachablenot dynamically scanned

    A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.

  • N/A
    Authentication Enforced (live)not dynamically scanned

    If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Tools (48)

CC#GoC++PHPJavaRubyRustRadonBanditCursorPythonWindsurfSingletoncodeseekerAudit (npm)InheritanceMVC PatternCode AnalysisVisual Studiosemantic-graphClaude Code CLIFactory PatternObserver PatternQuality EngineerSystem ArchitectReact Applicationcontext-optimizerRepository PatternTypeScript ProjectPython Syntax CheckSecurity SpecialistAnalysis CoordinatorPerformance EngineerService Layer PatternCode Analysis WorkflowProject InitializationInterface ImplementationSemantic Search WorkflowVS Code (GitHub Copilot)Code Quality Audit BundleDebugging Analysis BundleDeveloper Experience BundleArchitecture Analysis BundleCode Quality Analysis BundleEnterprise Compliance BundlePerformance Optimization Bundle${sourceNode.name} <-> ${targetNode.name}