The published @socketsecurity/mcp@0.0.18 package currently exposes repository metadata but not npm homepage or bugs metadata:
npm view @socketsecurity/mcp@0.0.18 name version homepage repository bugs --json
Observed result includes only:
{
name: @socketsecurity/mcp,
version: 0.0.18,
repository: {
url: https://github.com/SocketDev/socket-mcp,
type: git
}
}
Expected metadata would point npm users to the README and issue tracker, for example:
homepage: https://github.com/SocketDev/socket-mcp#readme
bugs.url: https://github.com/SocketDev/socket-mcp/issues
I prepared the one-file manifest patch here, but GitHub would not let this account open a cross-fork PR into SocketDev/socket-mcp:
Local validation:
- metadata smoke check for
homepage, bugs, and repository
git diff --check
The published
@socketsecurity/mcp@0.0.18package currently exposes repository metadata but not npmhomepageorbugsmetadata:Observed result includes only:
{ name: @socketsecurity/mcp, version: 0.0.18, repository: { url: https://github.com/SocketDev/socket-mcp, type: git } }Expected metadata would point npm users to the README and issue tracker, for example:
homepage:https://github.com/SocketDev/socket-mcp#readmebugs.url:https://github.com/SocketDev/socket-mcp/issuesI prepared the one-file manifest patch here, but GitHub would not let this account open a cross-fork PR into
SocketDev/socket-mcp:Local validation:
homepage,bugs, andrepositorygit diff --check