IDE extension community
Risk level
high
75/100

Continue ↗

Continue is a community-maintained IDE extension from Continue. Anomity scores its risk at 75 out of 100 (high). It matches 1 dangerous capability combination.

filesystem:read filesystem:write network:outbound credentials:access

Analysis summary

Continue is a community-maintained IDE extension from Continue. Anomity scores its risk at 75 out of 100 (high). It matches 1 dangerous capability combination.

Continue is an open-source IDE extension that brings autocomplete, chat, and inline edits to VS Code and JetBrains using any LLM provider or local model. It's distributed on the VS Code Marketplace and JetBrains Marketplace, with the core engine published under an Apache 2.0 license, so teams can self-host the model layer and audit what the extension does on disk.

Its declared capabilities include reading files in the open workspace and across configured context providers, writing edits back into source files when the user accepts a suggestion, making outbound network requests to the configured model and embedding providers, and accessing credentials stored in the IDE secret store. Continue does not request shell execution by default, which gives it a notably smaller blast radius than the fully-agentic extensions in the same category.

From a risk standpoint, the extension is community-maintained and pairs filesystem write with credentials access — enough to match the credential-theft dangerous combination — but lacks the shell-execute capability that would push it into exfiltration territory. Teams adopting Continue should restrict its model providers to vetted endpoints and avoid pointing it at credentials that are not scoped to the developer's workstation.

Why this entry scored 75 out of 100

This profile starts at the catalog's neutral base of 50. Because the entry is community-maintained, trust adjusts the score by -10. Declared high-risk capabilities add +20 (capped at +30). It matches 1 dangerous capability combination, which contributes additional severity weight. The clamped result is 75, placing it in the high band.

See the full scoring formula →

Findings

  • Established community project Trust offset
    Contribution to score: -10
  • 2 high-risk capabilities: filesystem:write, credentials:access Critical
    Contribution to score: +20
  • Credential theft risk (high) High
    Evidence
    Filesystem write combined with credentials access can plant persistent credential stealers.
    Contribution to score: +15

Capabilities

Every capability the entry declares, with the security implication of each.

  • filesystem:read Filesystem read
    Can read files on the host system. Used for context, indexing, or analysis.
  • filesystem:write Filesystem write
    Can create, edit, or delete files on the host system. High-impact capability — anything from helpful edits to planting persistence.
  • network:outbound Outbound network
    Can make outbound network requests. Required for hosted model providers and remote APIs; also the path for data exfiltration if combined with read access.
  • credentials:access Credentials access
    Reads provider API keys, OAuth tokens, or other secrets from the host keychain or environment.

Dangerous combinations matched

Capability pairings that compound into well-known attack patterns.

  • Credential theft risk high
    Filesystem write combined with credentials access can plant persistent credential stealers.
    filesystem:write credentials:access