Skip to content

[Feature]: Add maturity levels to plugins #1413

@tedhabeck

Description

@tedhabeck

📚 Documentation Issue Summary

Update plugins tables to include a column for plugin maturity


📍 Location of the Problem

https://ibm.github.io/mcp-context-forge/using/plugins/plugins/)

✏️ Type of Issue

  • Typo or formatting issue
  • Outdated or incorrect information
  • Missing explanation or example
  • Unclear instructions
  • Other (explain below)

💡 Suggested Fix or Clarification (optional)

A proposal for a plugin maturity model that reflects the stability and reliability of a given plugin based upon coverage as illustrated in the table below:

Plugin Maturity Model
level 1 A new plugin still under development. May not have unit tests, or integration tests. e.g. Alpha test code
level 2 A plugin with code coverage of upto 25% and at least one integration test, beta quality code
level 3 A plugin with code coverage of over 50% and at least one integration test, no detected vulnerabilities, feature, performance, or other ongoing development
level 4 A plugin with code coverage of over 75% and at least one integration test, no detected vulnerabilities, stable code base
level 5 A plugin with code coverage of over 80% and at least one integration test. no detected vulnerabilities, stable code base
<style>.redblock {background-color: red} .yellowblock {background-color: yellow; color: black;} .purpleblock {background-color: purple} .blueblock {background-color: blue} .greenblock {background-color: green}</style>
Unit tests Integration tests coverage > 80 % Vulnerabilities Open Bugs Documentation Stabilitiy
 level 1  
<n> Unstable
  level 2  
<n> Unstable
 level 3  
<n> Stable
  level 4  
<n> Stable
  level 5  
0 Stable

Add a column for the maturity level of the plugin e.g. level [1..5] from the table above to the plugins page.


🧠 Environment (optional)

If related to platform-specific behavior (e.g. a command not working on macOS), describe that here:

Key Value
Docs version latest, main
Docs build method e.g. mkdocs locally, GitHub Pages

🧩 Additional Notes (optional)

Any screenshots, logs, or related issues?

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationtriageIssues / Features awaiting triage

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions