Repository navigation
website: the open scoreboard of the scan, at /scoreboard - #108
Merged
Merged
Conversation
One row per measurement of how many known findings from closed contests the scan finds, each linking to the rule written before the run and the result after it. Pending rows (the sealed run, contests after today) stay empty on purpose. Rows on a set we tune on are labelled not evidence. A page section says what is open (contests, judges, rules, every output) and what stays private (how the scan finds things, whose files are committed by hash before the sealed run); a test fails if a row starts describing the recipe. Sitemap, llms.txt and the CTA of the blog post that reports the measurement point at it. Tests for the data and the page.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
tokenizen | df61e68 | Commit Preview URL Branch Preview URL |
Oct 24 2026, 04:03 PM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
tokenizen-website | df61e68 | Commit Preview URL Branch Preview URL |
Oct 24 2026, 04:04 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One row per measurement of how many known findings from closed contests the scan finds, each linking to the rule written before the run and the result after it (the development set results are now in the public repository, bug-bounty-intelligence-mcp#21). Pending rows (the sealed run, contests after today) stay empty on purpose. Rows on a set we tune on are labelled not evidence. A section says what is open (contests, judges, rules, every output) and what stays private (how the scan finds things; the hash of its files is committed before the sealed run), and a test fails if a row starts describing the recipe. Sitemap, llms.txt and the call to action of the blog post that reports the measurement point at it. Tests for the data and the page, typecheck and build pass; checked in a headless browser.