CanopiiCanopiiAll serversEnterprise →
io.github.elie222/inbox-zero

io.github.elie222/inbox-zero v0.1.0

Security Trust Score
Grade B · Moderate posture
Tier 1 · Public sourceHigh confidence · 90%
Declared MCP capabilities
ResourcesPrompts

Host io.github.elie222/inbox-zero in a governed environment — SSO in front, every tool call attributed and audited.

Reputation12kstars1.6kforks165open issuestodaylast commit3yage

Security controls

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

Model–MCP Runtime Guardrails

  • 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
    User-in-the-Loop / Approval Scopeguardno destructive tool scope

    No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.

  • N/A
    Tool Definition Integrityguardno prior version to diff

    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.

Application Security Checks

  • Warn
    No path traversalguard46 occurrences

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

    apps/desktop/__tests__/mail-engine/electron-local-renderer.test.ts:158apps/desktop/__tests__/mail-engine/electron-packaged-renderer.test.ts:84apps/desktop/__tests__/mail-engine/electron-session.test.ts:41apps/desktop/__tests__/mail-engine/recovery.test.ts:77

    Fix: Resolve to a canonical path and verify containment; reject ../ and symlinks.

  • Warn
    No SSRF sinksguard18 occurrences

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

    apps/desktop/src/mail-engine/request.ts:44apps/desktop/src/network-errors.test.ts:8apps/unsubscribe-worker/src/model.ts:29apps/unsubscribe-worker/src/runner.ts:48

    Fix: Allow-list destinations; reject arbitrary/loopback/link-local URLs.

  • 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
    Declares a licenseno recognized license

    A clear license is required for legal enterprise use.

    Fix: Add a recognized SPDX license (MIT, Apache-2.0, …).

  • 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 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
    Actively maintainedrecent commits

    Unmaintained servers don't receive security fixes.

  • Pass
    Repository not archivedguardactive

    Archived repositories will never be patched.

  • Pass
    Has a security policySECURITY.md present

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

  • 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
    No known-vulnerable dependenciesno lockfile found

    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.

  • Not checked
    Signed releasesnot evaluated

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

  • N/A
    No install/post-install scriptsguardno published package

    install hooks run arbitrary code on every consumer at install time.

  • N/A
    Package name not typosquattingguardno published package

    Names mimicking popular packages are a common malware delivery vector.

  • N/A
    Published with provenanceno published package

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

  • N/A
    Established maintainerno published package

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

Transport & Trust Model

  • Warn
    Network Exposurebinds 0.0.0.0

    Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.

    Fix: Bind to 127.0.0.1 by default; never ship open debug endpoints.

  • Pass
    Transport Encryption (TLS)guardall remotes use HTTPS

    Plaintext HTTP exposes traffic and bearer tokens to interception.

  • Pass
    IAM / Authentication ScopingOAuth / PRM handling detected

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

  • Pass
    Execution Sandboxingcontainerized

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

  • 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 (80)

ToneReceiptAccuracyReceiptsRestraintadd-tasksNewsletterfind-tasksConcisenessNewslettersVoice matchCompletenessNotificationfind-projectsCorrect FormatNo HallucinationKnowledge base useNo default em dashNo scheduling driftRefund context usedEmail body semanticsMeeting context usedVerification warningArchive rule conditionBooking link respectedCC exclusion semanticsCapability explanationForward note semanticsNo appended setup callSaved memory semanticsSearch query semanticsMemory search semanticsReply content semanticsSemantic aiInstructionsGrounded contract detailInvestigation commitmentReasonable Outlook retryRule condition semanticsSelected attachment usedSummarizes email contentCorrect decision recappedNo fabricated commitmentsNo invented meeting timesSemantic rule instructionsDigest delivery explanationKnowledge content semanticsOne concrete meeting proposalAccurate partial-action summaryInline image treated as presentPersonal instructions semanticsPhishing-aware legitimacy checkReasonable direct Outlook queryPre-deadline pricing context usedLabel and mark-read rule conditionNo perfect future-matching promiseNo stalling or drafter uncertaintyPost-deadline pricing context usedOne-Off Event Rule Suggestion InboxInconclusive fallback-only diagnosisHonest background executor limitationKnowledge base answer, no placeholderBooking link preferred over time slotsConcise contact-specific payment replyCurrent thread facts override examplesGrounded explanation for expected draftNo unsupported concrete pricing detailsCreated rule matches the confirmed scopeSafe handling of ambiguous inbox actionsComplete and grounded multi-part responseNo invented cause across repeated feedbackUnresolved non-payment status remains conciseDetects mismatch when unexpected draft appearsGrounded explanation from exact rule executionNo invented cause from empty execution historyRequested options with human-friendly timezoneDetects mismatch when expected draft is missingSender contradiction overrides stale resolutionNo hallucinated email lookup after search failureGrounded rule suggestions with priority calibrationPending confirmation from indirect retrieved content