{
 "schema_version": 1,
 "generated": "2026-10-26",
 "id": "wevm-frog--report-friction-to-dependency-maintainers",
 "repo": "wevm/frog",
 "repo_url": "https://github.com/wevm/frog",
 "repo_slug": "wevm-frog",
 "title": "Report friction in a dependency to its maintainers",
 "page_title": "How to report friction in a dependency to its maintainers with Frog",
 "summary": "Send a friction entry to an upstream project that has opted in, using its issue form.",
 "who": "A developer whose agent hits a bug or rough edge in an npm dependency and wants the maintainers to receive a structured report.",
 "problem": "Friction caused by a dependency stays in the local repository, so the project that could fix it never hears about it.",
 "outcome": "A friction entry targeted at an opted-in project, scaffolded from that project's GitHub issue form.",
 "steps": [
  "Run `frog targets` to list the dependencies that accept friction reports.",
  "Run `frog log --target viem` with the dependency name from the list, replacing viem with your target.",
  "Fill in the prompts so the scaffolded entry answers the target project's issue form questions.",
  "Run `frog list` to check that the entry shows its target.",
  "Run `frog publish` to report the pending entry to the target project."
 ],
 "agent_prompt": "In the frog repository, run `frog targets` and then `frog log --target <package>` for the dependency that caused the friction. Expected output: a targeted entry scaffolded from that project's issue form. Verify by running `frog list` and checking that the entry shows the target package.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "A dependency only receives reports if it has opted in through its repository, so a target missing from `frog targets` cannot be reported to with this workflow.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "typescript",
 "requirements": [
  "A GitHub repository for the project that the agent works in",
  "npm, pnpm, bun, or yarn, or the standalone executable from the install script",
  "A choice between the Frog GitHub App and Action-only mode, made with the user before access is changed",
  "A PostgreSQL connection string, only if you want a shared database store"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.9,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/wevm-frog/report-friction-to-dependency-maintainers/",
 "md": "https://dedupedai.com/use-cases/wevm-frog/report-friction-to-dependency-maintainers/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/wevm-frog--report-friction-to-dependency-maintainers.json",
 "api_version": "v1"
}