Package.json formatting issue prevents npm from displaying repository metadata

[jordanburke]

Problem

The package.json file contains malformed JSON with literal \n characters instead of actual newlines. This causes npm to fail parsing the repository metadata, resulting in the GitHub repository link not appearing in the npm package page sidebar.

Current State

The package.json file contains:

{\n  "name": "github-mcp-custom",\n  "version": "1.0.20",\n  ...

Instead of properly formatted JSON:

{
  "name": "github-mcp-custom",
  "version": "1.0.20",
  ...

Impact

• Repository link doesn't appear in npm package sidebar at https://www.npmjs.com/package/github-mcp-custom
• Potential issues with other npm tooling that relies on proper JSON parsing
• May affect automated tools that parse package metadata

Solution

The package.json needs to be reformatted with proper newlines. This has been fixed locally in version 1.0.21.

Steps to Reproduce

1. View the raw package.json file in version 1.0.20
2. Notice the literal \n characters throughout the file
3. Check https://www.npmjs.com/package/github-mcp-custom - repository link missing from sidebar

Expected Behavior

• Package.json should be properly formatted JSON
• Repository link should appear in npm package page sidebar
• All JSON parsers should be able to read the file without issues

Environment:

• Package version: 1.0.20
• npm registry: npmjs.com

[jordanburke]

#3

Great lib, it's exactly what I was looking for in regard to a local but more or less offical Github MCP - I was concern on NPM.js about not seeing the source code so I hunted it down via search and found the package issue - that should fix the url on NPM.js. Thanks!