Skip to content
Menu

bug-bounty-methodology

Uncategorised

Verified Builder
Development · what the builder is doing
ShippingLast ship 3d ago
Token
No token tracked
What HEY checked
Shipping.
Shipped something meaningful in the last 7 days.
No token tracked.
HEY tracks no token for this project.
Market figures are context only and never change activity status. Methodology
FollowCreate alertOpen in TerminalView latest shipOpen on X

What HEY knows

Build
DerivedShipping: 1 meaningful event in 30 days; last ship 3 days ago. Details Source
Product usage
FactNo contract is recorded for this project, so there is no on-chain usage to count. Details
Not yet known
Unknown5 gaps: Repository details (not enough yet), Published packages (not enough yet), Official docs (no source), +2 more. HEY has not read what its repositories declare yet. Details
Full research, market and contracts in the Terminal →
LinksGitHubSources

Latest ship

Active development: 66 commits in the last 90 days across 3 contributors

Code activitySource linked

8 active day(s) in satisloeb/bug-bounty-methodology.

This week: substance read on 29 commits of 42 (1 changed code, 28 could not be classified); HEY stops reading a week at its first commit that changes code.

View evidence ↗

Builder activity

Meaningful, source-backed updates per week. Commits are aggregated, not counted individually.

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

No published notes on bug-bounty-methodology yet.

    Know something about bug-bounty-methodology? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

    Sources