Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Installed MCP entry points serve the wrong framework or nothing: `darnit serve` picks the alphabetically first framework, and the plugin runner calls a nonexistent `darnit-mcp` executable

オープン
  • 何か問題がありますか？
#478 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
python
領域
build-system, cli

調査の方向性

Start by tracing the default selection in packages/darnit/src/darnit/cli.py and the runner commands in packaging/claude-plugin/templates/darnit-mcp-runner and plugin.json; compare them with the console-script declaration in packages/darnit/pyproject.toml and the meta-package pyproject.toml. Reproduce the reported commands, then check release-smoke.yml’s runner check; done means installed configs launch successfully and bare serve has an intentional framework-selection behavior.

索引モデルが issue の本文から書いたものです。

説明

infrastructure interface-cli interface-mcp

Summary

Two defects in how the MCP server is launched from installed configs:

  1. darnit serve with no --framework and no config path serves list_available_frameworks()[0], which is sorted by name. With the published darnit-mcp meta-package (darnit-baseline, darnit-gittuf, darnit-reproducibility) that is gittuf, not openssf-baseline. darnit install writes exactly that bare command into the client config, so the skills' audit_openssf_baseline tool is absent. In the dev workspace it resolves to community-spec.
  2. The Claude Code plugin runner executes uvx --from darnit-mcp==$V darnit-mcp (and pipx run darnit-mcp==$V). darnit-mcp is a metadata-only wheel with no console scripts; the only script, darnit, lives in darnit-core. The runner also passes no serve subcommand (plugin.json args are []).

Impact

A user following either install path gets an MCP server for the wrong framework, or none. The skills then report "no audit tools" or audit against an unintended standard.

Evidence

Reproduction

$ uvx --from darnit-mcp==0.1.0 darnit-mcp --help
Package `darnit-mcp` does not provide any executables.        (exit 1)

$ uvx --from darnit-mcp==0.1.0 python -c "from darnit.config import list_available_frameworks as f; print(f())"
['gittuf', 'openssf-baseline', 'reproducibility']

The published darnit_mcp-0.1.0-py3-none-any.whl contains only dist-info files and no entry_points.txt. Expected: the runner starts a server, and a bare darnit serve serves an intended framework. Actual: the runner fails; darnit serve serves gittuf.

Suggested direction

  • Make serve without --framework either fail with the list of choices or serve all installed frameworks; have darnit install write an explicit --framework (or config path).
  • Give darnit-mcp a darnit-mcp console script (or change the runner to --from darnit-mcp==$V darnit serve --framework ...), and add a smoke test that runs the runner against a built wheel before release.
  • Related: #229, #231, #389.
主要言語
Python
スター
22
フォーク
27
平均マージ
2日 28分
マージ済み PR（30日）
40

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

darnitdevorg/darnit のほかの issue

darnitdevorg/darnit の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。