Enterprise DNAEnterprise DNA

Skills

poidh-bounty

by picsoritdidnthappen

Post bounties, discover and inspect bounties, submit claims, evaluate submissions, and accept or nominate winning claims on poidh (pics or it didn't happen) on Ethereum…

Our verdict

Not reviewed yet

We have not reviewed poidh-bounty yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About poidh-bounty

poidh-bounty is a TypeScript skill for interacting with poidh (pics or it didn't happen) bounties on Ethereum Mainnet, Arbitrum, or Base. It enables posting bounties with ETH rewards, discovering and inspecting existing bounties, submitting claims, evaluating submissions, and accepting or nominating winning claims. It also supports initiating or resolving voting on open bounties, querying poidh data, and withdrawing winnings.

Best for

Developers building tools that manage on-chain bounty workflows on poidh.

Use cases

  • Create a new on-chain bounty with an ETH reward on poidh.xyz
  • Find and inspect available bounties across supported networks
  • Submit proof to an existing bounty and evaluate submissions
  • Accept a winning claim or initiate voting on an open bounty

Notes

40 stars on GitHub. Last updated 2026-11-05. Licensed MIT.

Pros

  • Supports multiple networks (Ethereum Mainnet, Arbitrum, Base)
  • Covers full bounty lifecycle from creation to payout
  • Integrates with vision and content tools for evaluating submissions

Cons

  • Limited to poidh platform bounties
  • Requires ETH for rewards and gas fees
  • Dependent on network conditions and smart contract behavior

Key facts

What we have checked

Days since the last commit
0
Checked GitHub
GitHub forks
75
Checked GitHub
GitHub stars
41
Checked GitHub
Days to a first reply on issues
37.5
Checked GitHub
Open issues
21
Checked GitHub
Releases in the last 90 days
0
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

Stars and usage

How poidh-bounty is growing

GitHub stars

40 to 41

stars. 1 Nov 2026 to 14 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is poidh-bounty looked after, and what do its setup files show

Health score

38 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity30 of 30Last push 0 days ago
Releases0 of 150 releases in 90 days
Issue replies0 of 20First reply in 37.5 days (median)
Maintainer0 of 15Owned by a single user
Official sourceNot countedMCP servers only

Security check static checks

40 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-skill-static-v1 prod@c6b5b7408b8c. What it checks

  • Critical Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used (affects next 13.5.3, pinned in package.json).
  • Critical Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used (affects next 13.5.3, pinned in package.json).
  • Critical Authorization Bypass in Next.js Middleware (affects next 13.5.3, pinned in package.json).
  • Critical Next.js: Unauthenticated Remote Code Execution on windows-hosted servers (affects next 13.5.3, pinned in package.json).
  • High Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n (affects next 13.5.3, pinned in package.json).
  • High Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up (affects next 13.5.3, pinned in package.json).
  • High Next.js authorization bypass vulnerability (affects next 13.5.3, pinned in package.json).
  • High Next.js Vulnerable to Denial of Service with Server Components (affects next 13.5.3, pinned in package.json).
  • High Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades (affects next 13.5.3, pinned in package.json).
  • High Next.js Server-Side Request Forgery in Server Actions (affects next 13.5.3, pinned in package.json).
  • High Next.js Cache Poisoning (affects next 13.5.3, pinned in package.json).
  • High Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components (affects next 13.5.3, pinned in package.json).
  • High Next.js: Denial of Service in App Router using Server Actions (affects next 13.5.3, pinned in package.json).
  • High Next Vulnerable to Denial of Service with Server Components (affects next 13.5.3, pinned in package.json).
  • High Next.js: Denial of Service in App Router using Server Actions (affects next 13.5.3, pinned in package.json).
  • High Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname (affects next 13.5.3, pinned in package.json).
  • High Next.js has a Denial of Service with Server Components (affects next 13.5.3, pinned in package.json).
  • Medium Next.js: Unbounded next/image disk cache growth can exhaust storage (affects next 13.5.3, pinned in package.json).
  • Medium Next.js Improper Middleware Redirect Handling Leads to SSRF (affects next 13.5.3, pinned in package.json).
  • Medium Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences (affects next 13.5.3, pinned in package.json).
  • Medium Next.js: Unbounded Server Action payload in Edge runtime (affects next 13.5.3, pinned in package.json).
  • Medium Next.js: Cache confusion of response bodies for requests with bodies (affects next 13.5.3, pinned in package.json).
  • Medium Next.js Allows a Denial of Service (DoS) with Server Actions (affects next 13.5.3, pinned in package.json).
  • Medium Next.js: Unauthenticated disclosure of internal Server Function endpoints (affects next 13.5.3, pinned in package.json).
  • Medium Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration (affects next 13.5.3, pinned in package.json).
  • Medium Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces (affects next 13.5.3, pinned in package.json).
  • Medium Next.js Affected by Cache Key Confusion for Image Optimization API Routes (affects next 13.5.3, pinned in package.json).
  • Medium Denial of Service condition in Next.js image optimization (affects next 13.5.3, pinned in package.json).
  • Medium Next.js: HTTP request smuggling in rewrites (affects next 13.5.3, pinned in package.json).
  • Medium Next.js has cross-site scripting in beforeInteractive scripts with untrusted input (affects next 13.5.3, pinned in package.json).
  • Medium Next.js has a Denial of Service in the Image Optimization API (affects next 13.5.3, pinned in package.json).
  • Medium Next.js Content Injection Vulnerability for Image Optimization (affects next 13.5.3, pinned in package.json).
  • Low Next.js's Middleware / Proxy redirects can be cache-poisoned (affects next 13.5.3, pinned in package.json).
  • Low Information exposure in Next.js dev server due to lack of origin verification (affects next 13.5.3, pinned in package.json).
  • Low Next.js Race Condition to Cache Poisoning (affects next 13.5.3, pinned in package.json).
  • Low Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting (affects next 13.5.3, pinned in package.json).
  • Note 159 files were not read (over 512 KB, or past the 60 file cap): pnpm-lock.yaml, src/utils/share.ts, src/utils/types.ts and more.
  • Note 51 of 60 packages are not pinned to one version, so only the malicious packages list was checked for them, not version advisories.

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Days to a first reply on issues, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

  1. Security finding

    Source: osv.dev

  2. Security finding

    Source: osv.dev

  3. Security finding

    Source: osv.dev

  4. Security finding

    Source: osv.dev

  5. Security finding

    Source: osv.dev

  6. Security finding

    Source: osv.dev

  7. Security finding

    Source: osv.dev

  8. Security finding

    Source: osv.dev

  9. Security finding

    Source: osv.dev

  10. Security finding

    Source: osv.dev

  11. Security finding

    Source: osv.dev

  12. Security finding

    Source: osv.dev

  13. Security finding

    Source: osv.dev

  14. Security finding

    Source: osv.dev

  15. Security finding

    Source: osv.dev

  16. Security finding

    Source: osv.dev

  17. Security finding

    Source: osv.dev

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.