io.github.qwertymuzaffar/udacity-commit
NPM · MCP-UDACITY-COMMIT · SCANNED AUG 3
Validate & format git commit messages per the Udacity Git Commit Message Style Guide.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 275 tokens (~55/item across 5 items; 3 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · mcp-udacity-commit
claude mcp add qwertymuzaffar-udacity-commit -- npx -y mcp-udacity-commit
codex mcp add qwertymuzaffar-udacity-commit -- npx -y mcp-udacity-commit
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"qwertymuzaffar-udacity-commit": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-udacity-commit"
],
"enabled": true
}
}
} openclaw mcp add qwertymuzaffar-udacity-commit --command npx --arg -y --arg mcp-udacity-commit
mcp_servers:
qwertymuzaffar-udacity-commit:
command: "npx"
args: ["-y", "mcp-udacity-commit"] {
"mcpServers": {
"qwertymuzaffar-udacity-commit": {
"command": "npx",
"args": [
"-y",
"mcp-udacity-commit"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +40
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 31 Jul 26 +20
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
- Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
- 28 Jul 26 6
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
format_commit_message Format a Udacity-style commit message ~103
Compose a compliant commit message from its parts. The subject is capitalized, a trailing period is removed, and the body is wrapped at 72 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | — | What & why; auto-wrapped at 72 chars |
| footer | string | — | Issue refs, e.g. "Resolves: #123" |
| subject | string | yes | Imperative subject; auto-capitalized, trailing period removed |
| type | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | — |
| problems | array | yes | — |
| valid | boolean | yes | — |
| warnings | array | yes | — |
No examples provided.
validate_branch_name Validate a git branch name ~79
Check a git branch name against the companion type/kebab-case convention (e.g. "feat/add-dark-mode"). Returns whether it is compliant plus any problems (violations) and warnings (hints). Base branches like main/master are exempt.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The branch name to check, e.g. "feat/add-dark-mode" |
| Name | Type | Req | Description |
|---|---|---|---|
| problems | array | yes | — |
| valid | boolean | yes | — |
| warnings | array | yes | — |
No examples provided.
validate_commit_message Validate a commit message ~54
Check a commit message against the Udacity Git Commit Message Style Guide. Returns whether it is compliant plus any problems (violations) and warnings (hints).
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The full commit message to check |
| Name | Type | Req | Description |
|---|---|---|---|
| problems | array | yes | — |
| valid | boolean | yes | — |
| warnings | array | yes | — |
No examples provided.