---
title: "opencode-studio trust report"
type: "trust-report"
slug: "microck-opencode-studio"
canonical_url: "https://www.graphcanon.com/tools/microck-opencode-studio/trust"
computed_at: "2026-07-11T11:54:52.904Z"
maintenance_label: "Very active"
security_status: "no_manifest"
---

# opencode-studio trust report

_Sourced [trust signals](/glossary/trust-and-signals/trust-signal) from public GitHub metadata and optional dependency [security scans](/glossary/trust-and-signals/security-scan). Not a security guarantee._

## Maintenance

- Label: Very active (96% recency signal)
- Days since last push: 0
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 1124936542
- Not a fork
- Owner type: User
- Computed at: 2026-07-11T11:54:52.904Z
- Methodology: github_public_v1

## Security scan

- Status: No MCP manifest (0 critical, 0 high, 0 medium, 0 low) · last scan 2026-07-11T11:54:53.462Z

## Method and caveats

These are heuristics from public GitHub data and optional dependency scans, sourced and dated. 
"No criticals found on 2026-07-11" is not a guarantee of safety.
See the full methodology: [/trust-methodology](/trust-methodology.md).

## Common questions

### Is opencode-studio maintained?

GraphCanon rates opencode-studio "Very active" (96% maintenance signal from public GitHub metadata, computed today). Last push was 0 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.

### Is opencode-studio safe to use?

Last scanned today (mcp_manifest profile). Status: No MCP manifest. Absence of findings in our scan is not a security guarantee - see [trust methodology](/trust-methodology) for scope limits. GraphCanon does not certify opencode-studio as safe - review maintenance, provenance, and scan findings on this page before adopting.

### Is opencode-studio a fork?

No. opencode-studio is not flagged as a fork in GitHub metadata at the time of the last refresh.

### Does opencode-studio have known security vulnerabilities?

Last scanned today (mcp_manifest profile). Status: No MCP manifest. Absence of findings in our scan is not a security guarantee - see [trust methodology](/trust-methodology) for scope limits.

### How often is the opencode-studio trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1).

### What does GraphCanon never claim about opencode-studio?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for opencode-studio. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology).

### How does GraphCanon assess trust for opencode-studio?

Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read [trust methodology](/trust-methodology) for full scope and limits.

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/tools/microck-opencode-studio/trust`](/api/graphcanon/tools/microck-opencode-studio/trust)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_