Requesting Private Vulnerability Reporting be enabled (security report ready)

Open
  • Is something wrong?
#11 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
20/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github
Domain
security

Research direction

Review GitHub's Private Vulnerability Reporting setting for cloudinary/structured-metadata-mcp and compare it with cloudinary/asset-management-mcp. Done means enabling private reporting or providing the requested security contact channel so the reporter can submit the vulnerability confidentially.

Written by the indexing model from the issue text.

Description

Hi cloudinary maintainers,

I found a security vulnerability in this repository (same bug class already reported, open and unmerged, on two sibling MCP server repos: cloudinary/account-provisioning-mcp#1 and cloudinary/analysis-mcp#1) and would like to report it responsibly. Could you enable GitHub's Private Vulnerability Reporting for this repo so I can file a private advisory? It's already enabled on cloudinary/asset-management-mcp, which received the same request.

If you'd prefer a different channel, a security contact email works too — I'm happy to hold the report under a standard 90-day disclosure window either way.

Thanks,
Syed Anas Mohiuddin

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
58m
Merged PRs (30d)
2

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.