anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Question: Ecosystem Curation Policy and Long-term Sustainability #8354

New Issue
Open
opened 2026-02-16 18:09:45 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:09:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @davidbernat on GitHub (Feb 2, 2026).

Originally assigned to: @thdxr on GitHub.

Question: Ecosystem Curation Policy and Long-term Sustainability

We are evaluating OpenCode for financial services development and need clarity on ecosystem management policies:

1. Curation vs Endorsement

Are ecosystem listings on https://opencode.ai/docs/ecosystem/ considered endorsements by the OpenCode team, or are they merely curated community submissions? This distinction is important for our enterprise risk assessment and compliance requirements.

2. Long-term Sustainability Support

Does OpenCode provide any assistance or guarantees for long-term reliability and short-term sustainability of listed packages? Specifically:

  • Maintenance monitoring for critical packages
  • Security vulnerability tracking
  • Update coordination for dependencies
  • Support for abandoned packages

3. Missing Categories - Research Agents

We notice that research agents appear to be absent from ecosystem listings, despite research being a critical workflow component. Is this:

  • An intentional omission (research handled differently)?
  • An oversight in current listings?
  • Coming in future updates?

Context

We're a 30-person financial services company requiring:

  • Enterprise-grade reliability guarantees
  • Long-term package sustainability
  • Comprehensive workflow coverage including research
  • Clear understanding of ecosystem support policies

This information will significantly impact our adoption decision and internal development strategy.

Thank you for clarification on these important enterprise considerations.

Originally created by @davidbernat on GitHub (Feb 2, 2026). Originally assigned to: @thdxr on GitHub. ## Question: Ecosystem Curation Policy and Long-term Sustainability We are evaluating OpenCode for financial services development and need clarity on ecosystem management policies: ### 1. Curation vs Endorsement Are ecosystem listings on https://opencode.ai/docs/ecosystem/ considered **endorsements** by the OpenCode team, or are they merely **curated community submissions**? This distinction is important for our enterprise risk assessment and compliance requirements. ### 2. Long-term Sustainability Support Does OpenCode provide any assistance or guarantees for **long-term reliability and short-term sustainability** of listed packages? Specifically: - Maintenance monitoring for critical packages - Security vulnerability tracking - Update coordination for dependencies - Support for abandoned packages ### 3. Missing Categories - Research Agents We notice that **research agents** appear to be absent from ecosystem listings, despite research being a critical workflow component. Is this: - An intentional omission (research handled differently)? - An oversight in current listings? - Coming in future updates? ### Context We're a 30-person financial services company requiring: - Enterprise-grade reliability guarantees - Long-term package sustainability - Comprehensive workflow coverage including research - Clear understanding of ecosystem support policies This information will significantly impact our adoption decision and internal development strategy. Thank you for clarification on these important enterprise considerations.
yindo added the docs label 2026-02-16 18:09:45 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label docs
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8354
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?