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
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.
From the listing
About poidh-bounty
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 Mainnet, Arbitrum, or Base. Use this skill when the user wants to create a bounty on poidh.xyz, find available bounties, post a task with an ETH reward on-chain, submit proof to an existing bounty, evaluate submissions using vision or other content tools, accept a winning claim on a solo bounty, initiate/resolve voting on an open bounty, query poidh data, or withdraw bounty winnings.
Notes
poidh-bounty — finance from picsoritdidnthappen.
39 stars on GitHub. Last updated 2026-10-25. Licensed MIT.
Indexed from github-skill-md. Verified against the live GitHub repo.
Key facts
What we have checked
Not checked yet. Dated facts such as prices, releases and repository activity appear here once we have confirmed them from a source.
Health and security
Is poidh-bounty looked after, and what do its setup files show
Security check static checks
40 out of 100
- 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
No sources recorded yet. Each source we check is listed here with the date we checked it.
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
Security finding
Security finding
Security finding
Security finding
Security finding
Security finding
Security finding
Security finding
Security finding
Security finding
Security finding
Security finding
Security finding
Security finding
Security finding
Security finding
Security finding
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.