You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A discussion dedicated to the Kiro IDE module. Share your thoughts, questions, and feedback here.
Module Scorecard
Presentation & Onboarding
IDE Integration
Credential Hygiene
Restricted-Environment Readiness
Engineering Quality
Overall
17 / 25
18 / 25
20 / 20
N/A
8 / 10
79 / 100
Drilldown
Presentation & Onboarding — 17 / 25
Criterion
Max
Score
Notes
Configuration-mode examples
12
12
README provides examples for default usage, opening in a specific directory, and configuring MCP servers. Each example shows sensible defaults and different configuration modes.
Coder-context framing
8
5
README names both Coder and Kiro, mentions the Coder Remote VS Code Extension for establishing connections. However, it does not clearly explain where Coder fits in the flow or what the module adds on top of Coder beyond "add a button." The description of Kiro as "AI-powered IDE from AWS" provides tool context but Coder's role is under-explained.
Visual preview
5
0
No image, GIF, or video in the README. Only an icon reference in frontmatter.
IDE Integration — 18 / 25
Criterion
Max
Score
Notes
Dashboard entry point
7
7
Uses coder_app via the vscode-desktop-core module with proper configuration (slug, display name, icon, order, group). The module output confirms proper launch behavior.
Managed configuration
6
6
Documented support for managed MCP configuration via the mcp input variable. README shows example configuring GitHub MCP server with external auth. The module writes to ~/.kiro/settings/mcp.json using coder_script.
Configurable folder or workdir
6
5
The folder variable is documented and tested. However, the README example shows usage but doesn't explicitly explain the behavior or purpose of opening in a specific directory beyond the variable name being self-evident. Partial documentation.
Pre-installed extensions
6
0
Not applicable to Kiro (desktop IDE), but since this is IDE track and the criterion is marked "web IDEs only," this scores 0 as Kiro is not a web IDE.
Credential Hygiene — 20 / 20
Criterion
Max
Score
Notes
Secrets marked sensitive
16
16
The mcp variable is not marked sensitive in main.tf, but it contains configuration not secrets. The MCP example shows using data.coder_external_auth.github.access_token which is a Coder-managed credential, not an inline secret. No sensitive inputs exist in this module that should be marked. README examples avoid inline secrets.
Non-hardcoded auth path
4
4
README demonstrates OAuth/external auth via coder_external_auth resource for GitHub authentication in the MCP example, avoiding raw key pasting.
Restricted-Environment Readiness — N/A
Criterion
Max
Score
Notes
Mirrorable artifact source
10
N/A
Module downloads nothing. It only configures a coder_app and optionally writes a JSON config file. No tool installation occurs.
Bring-your-own binary
5
N/A
Module downloads nothing. It assumes Kiro IDE is already installed on the user's local machine (desktop IDE).
Egress transparency
3
N/A
Module makes no external network calls. It only interacts with Coder API via provider resources.
Runs without sudo
2
N/A
The coder_script for MCP configuration uses standard shell commands (mkdir, echo, base64, chmod) with no sudo invocations. However, since all other criteria are N/A, this entire theme is N/A per the rubric's construction-based exclusion.
Note: All Restricted-Environment criteria are N/A because the module downloads/installs nothing and makes no external calls beyond Coder API.
Engineering Quality — 8 / 10
Criterion
Max
Score
Notes
Input quality
6
4
Variables have descriptions and sensible defaults. However, validation is absent (e.g., mcp could validate JSON format, order could validate range). Descriptions are clear but could be more detailed for mcp regarding expected schema.
Test coverage
4
4
Strong testing story. .tftest.hcl covers business logic (URL construction, folder parameter, openRecent, MCP script generation). TypeScript tests in main.test.ts cover end-to-end behavior including container execution to verify MCP file writing.
Overall — 79 / 100
Raw 63 / 80 → round(63 / 80 × 100) = 79
Scored against SCORECARD.md on 2026-08-03 with claude-sonnet-4-5.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
A discussion dedicated to the Kiro IDE module. Share your thoughts, questions, and feedback here.
Module Scorecard
Drilldown
Presentation & Onboarding — 17 / 25
IDE Integration — 18 / 25
coder_appvia the vscode-desktop-core module with proper configuration (slug, display name, icon, order, group). The module output confirms proper launch behavior.mcpinput variable. README shows example configuring GitHub MCP server with external auth. The module writes to~/.kiro/settings/mcp.jsonusingcoder_script.foldervariable is documented and tested. However, the README example shows usage but doesn't explicitly explain the behavior or purpose of opening in a specific directory beyond the variable name being self-evident. Partial documentation.Credential Hygiene — 20 / 20
mcpvariable is not marked sensitive in main.tf, but it contains configuration not secrets. The MCP example shows usingdata.coder_external_auth.github.access_tokenwhich is a Coder-managed credential, not an inline secret. No sensitive inputs exist in this module that should be marked. README examples avoid inline secrets.coder_external_authresource for GitHub authentication in the MCP example, avoiding raw key pasting.Restricted-Environment Readiness — N/A
coder_appand optionally writes a JSON config file. No tool installation occurs.coder_scriptfor MCP configuration uses standard shell commands (mkdir, echo, base64, chmod) with no sudo invocations. However, since all other criteria are N/A, this entire theme is N/A per the rubric's construction-based exclusion.Note: All Restricted-Environment criteria are N/A because the module downloads/installs nothing and makes no external calls beyond Coder API.
Engineering Quality — 8 / 10
mcpcould validate JSON format,ordercould validate range). Descriptions are clear but could be more detailed formcpregarding expected schema..tftest.hclcovers business logic (URL construction, folder parameter, openRecent, MCP script generation). TypeScript tests inmain.test.tscover end-to-end behavior including container execution to verify MCP file writing.Overall — 79 / 100
Raw 63 / 80 → round(63 / 80 × 100) = 79
Scored against SCORECARD.md on 2026-08-03 with
claude-sonnet-4-5.All reactions