SALT-NLP/Design2Code-HARD
This dataset consists of 80 extra difficult webpages from Github Pages, which challenges SoTA multimodal LLMs on converting visual designs into code implementations. Each example is a pair of source HTML and screenshot ({id}.html and {id}.png). See the "easy" version of the Design2Code testset here Note that all images in these webpages are replaced by a placeholder image (rick.jpg) Please refer to our project page and our paper for more information.
6379
1<!DOCTYPE html>2<html lang="en-US">3 <head>4 <style>5 6 7 8html, body, div, span, applet, object, iframe,9h1, h2, h3, h4, h5, h6, p, blockquote, pre,10a, abbr, acronym, address, big, cite, code,11del, dfn, em, img, ins, kbd, q, s, samp,12small, strike, strong, sub, sup, tt, var,13b, u, i, center,14dl, dt, dd, ol, ul, li,15fieldset, form, label, legend,16table, caption, tbody, tfoot, thead, tr, th, td,17article, aside, canvas, details, embed,18figure, figcaption, footer, header, hgroup,19menu, nav, output, ruby, section, summary,20time, mark, audio, video {21 padding: 0;22 margin: 0;23 font: inherit;24 font-size: 100%;25 vertical-align: baseline;26 border: 0;27}28/* HTML5 display-role reset for older browsers */29article, aside, details, figcaption, figure,30footer, header, hgroup, menu, nav, section {31 display: block;32}33body {34 line-height: 1;35}36ol, ul {37 list-style: none;38}39blockquote, q {40 quotes: none;41}42blockquote:before, blockquote:after,43q:before, q:after {44 content: '';45 content: none;46}47table {48 border-spacing: 0;49 border-collapse: collapse;50}51body {52 font-family: 'Helvetica Neue', Helvetica, Arial, serif;53 font-size: 13px;54 line-height: 1.5;55 color: #000;56}57 58a {59 font-weight: bold;60 color: #d5000d;61}62 63header {64 padding-top: 35px;65 padding-bottom: 10px;66}67 68header h1 {69 font-size: 48px;70 font-weight: bold;71 line-height: 1.2;72 color: #303030;73 letter-spacing: -1px;74}75 76header h2 {77 font-size: 24px;78 font-weight: normal;79 line-height: 1.3;80 color: #aaa;81 letter-spacing: -1px;82}83#downloads {84 display: none;85}86#main_content {87 padding-top: 20px;88}89 90code, pre {91 margin-bottom: 30px;92 font-family: Monaco, "Bitstream Vera Sans Mono", "Lucida Console", Terminal;93 font-size: 12px;94 color: #222;95}96 97code {98 padding: 0 3px;99}100 101pre {102 padding: 20px;103 overflow: auto;104 border: solid 1px #ddd;105}106pre code {107 padding: 0;108}109 110ul, ol, dl {111 margin-bottom: 20px;112}113 114 115/* COMMON STYLES */116 117table {118 width: 100%;119 border: 1px solid #ebebeb;120}121 122th {123 font-weight: 500;124}125 126td {127 font-weight: 300;128 text-align: center;129 border: 1px solid #ebebeb;130}131 132form {133 padding: 20px;134 background: #f2f2f2;135 136}137 138 139/* GENERAL ELEMENT TYPE STYLES */140 141h1 {142 font-size: 2.8em;143}144 145h2 {146 margin-bottom: 8px;147 font-size: 22px;148 font-weight: bold;149 color: #303030;150}151 152h3 {153 margin-bottom: 8px;154 font-size: 18px;155 font-weight: bold;156 color: #d5000d;157}158 159h4 {160 font-size: 16px;161 font-weight: bold;162 color: #303030;163}164 165h5 {166 font-size: 1em;167 color: #303030;168}169 170h6 {171 font-size: .8em;172 color: #303030;173}174 175p {176 margin-bottom: 20px;177 font-weight: 300;178}179 180a {181 text-decoration: none;182}183 184p a {185 font-weight: 400;186}187 188blockquote {189 padding: 0 0 0 30px;190 margin-bottom: 20px;191 font-size: 1.6em;192 border-left: 10px solid #e9e9e9;193}194 195ul li {196 list-style-position: inside;197 list-style: disc;198 padding-left: 20px;199}200 201ol li {202 list-style-position: inside;203 list-style: decimal;204 padding-left: 3px;205}206 207dl dd {208 font-style: italic;209 font-weight: 100;210}211 212footer {213 padding-top: 20px;214 padding-bottom: 30px;215 margin-top: 40px;216 font-size: 13px;217 color: #aaa;218}219 220footer a {221 color: #666;222}223 224/* MISC */225.clearfix:after {226 display: block;227 height: 0;228 clear: both;229 visibility: hidden;230 content: '.';231}232 233.clearfix {display: inline-block;}234* html .clearfix {height: 1%;}235.clearfix {display: block;}236 </style>237 <meta charset="utf-8">238 <meta content="width=device-width, initial-scale=1" name="viewport">239 <meta content="IE=edge" http-equiv="X-UA-Compatible">240 <!--[if lt IE 9]>241 242 <![endif]-->243 <!-- Begin Jekyll SEO tag v2.8.0 -->244 <title>245 OWASP needs to evolve | owasp-change.github.io246 </title>247 <meta content="Jekyll v3.9.3" name="generator">248 <meta content="OWASP needs to evolve" property="og:title">249 <meta content="en_US" property="og:locale">250 <meta content="An Open Letter to the OWASP Board" name="description">251 <meta content="An Open Letter to the OWASP Board" property="og:description">252 <meta content="" property="og:url">253 <meta content="owasp-change.github.io" property="og:site_name">254 <meta content="website" property="og:type">255 <meta content="summary" name="twitter:card">256 <meta content="OWASP needs to evolve" property="twitter:title">257 <!-- End Jekyll SEO tag -->258 <!-- start custom head snippets, customize with your own _includes/head-custom.html file -->259 <!-- Setup Google Analytics -->260 <!-- You can set your favicon here -->261 <!-- link rel="shortcut icon" type="image/x-icon" -->262 <!-- end custom head snippets -->263 </head>264 <body>265 <div id="container">266 <div class="inner">267 <header>268 <h1>269 OWASP needs to evolve270 </h1>271 <h2>272 An Open Letter to the OWASP Board273 </h2>274 </header>275 <section class="clearfix" id="downloads">276 </section>277 <hr>278 <section id="main_content">279 <h1 id="owasp-needs-to-evolve">280 OWASP needs to evolve281 </h1>282 <p>283 To the284 <a>285 OWASP Board of Directors286 </a>287 and the Executive Director of the OWASP Foundation,288 </p>289 <p>290 <a>291 OWASP292 </a>293 was first set up over two decades ago. The Internet, the way we build software, and the security industry, has changed so much that those days are hardly recognizable today.294 </p>295 <p>296 As a group of OWASP flagship project leaders and lifelong contributors, we believe that OWASP hasn’t kept pace and evolved to support the needs of important parts of our community today, especially our flagship projects. What worked in the past simply isn’t working now and OWASP needs to change.297 </p>298 <p>299 We have written and published this open letter, knowing that other parts of the community also support our concerns, and are asking the OWASP Board of Directors to take action. Year after year, concerns have been raised and there have been promises of change, but year after year it hasn’t happened.300 </p>301 <p>302 Today, many projects operate independently, in some cases managing their own sponsorships, finance, websites, domains, communication platforms, and developer tools. Projects still operate on a best-efforts model that relies on a few individuals working in their spare time.303 </p>304 <p>305 Without active world class projects, OWASP doesn’t have a unique selling point and projects need constant guidance, mentoring, and investment for them to grow and keep the brand where it should be: First and foremost for all things application security.306 </p>307 <p>308 There are five key areas that we feel if not addressed immediately, will result in important projects, like ours, leaving OWASP in search of, or creating a community that better meets their needs. We don’t want that to happen.309 </p>310 <ol>311 <li>312 The Foundation should publish and maintain a community plan that should include its prioritized key project initiatives, along with a suitable funding plan to support them. The313 <a>314 OSSF plan315 </a>316 is a useful example to reference.317 </li>318 <li>319 The Foundation’s governance structure should better reflect the needs of the entire security community, increasing access and participation for corporate practitioners, governments, major sponsors, and key technology providers. We believe this can be achieved with vendor independence and is particularly necessary to attract financial sponsorship and key industry partnerships.320 </li>321 <li>322 The Foundation’s funding should reflect the needs of our and other flagship projects to both sustain and improve them. We believe this would likely be in the region of five to ten million dollars per year for our projects alone.323 </li>324 <li>325 The Foundation should provide improved infrastructure and services to the community so that projects can focus on the projects themselves.326 </li>327 </ol>328 <p>329 This letter is written with positive intent and we believe is in the best interests of the OWASP community and those that rely on it. We appreciate that this is a change from how OWASP operates today, but have conviction that OWASP is at a tipping point and needs to evolve now.330 </p>331 <p>332 We all want to be part of the OWASP community and for it to continue to be successful in the decades to come.333 </p>334 <p>335 We ask that you respond within 30 days, with a plan of action to address the five points above.336 </p>337 <p>338 Yours truly,339 </p>340 <p>341 Simon Bennetts,342 <a>343 OWASP ZAP344 </a>345 founder and co-project leader,346 <a>347 OWASP VWAD348 </a>349 co-project leader350 <br>351 Ricardo Pereira,352 <a>353 OWASP ZAP354 </a>355 co-project leader356 <br>357 Glenn ten Cate,358 <a>359 Security Knowledge Framework360 </a>361 founder and co-project leader & OWASP Board Member362 <br>363 Akshath Kothari,364 <a>365 OWASP ZAP366 </a>367 core team member368 <br>369 Mark Curphey, OWASP founder and 2023 board member370 <br>371 Daniel Cuthbert,372 <a>373 OWASP ASVS374 </a>375 <br>376 Sebastien Deleersnyder,377 <a>378 OWASP SAMM379 </a>380 co-project leader and381 <a>382 OWASP Threat Modeling Playbook (OTMP)383 </a>384 founder and project leader385 <br>386 Bart De Win,387 <a>388 OWASP SAMM389 </a>390 co-project leader391 <br>392 Maxim Baele,393 <a>394 OWASP SAMM395 </a>396 core team member397 <br>398 Rick Mitchell,399 <a>400 OWASP ZAP401 </a>402 co-project leader,403 <a>404 OWASP Web Security Testing Guide405 </a>406 co-project leader,407 <a>408 OWASP VWAD409 </a>410 co-project leader411 <br>412 Steve Springett,413 <a>414 OWASP CycloneDX415 </a>416 and417 <a>418 OWASP Dependency-Track419 </a>420 founder and co-project leader421 <br>422 Patrick Dwyer,423 <a>424 OWASP CycloneDX425 </a>426 co-project leader427 <br>428 Björn Kimminich,429 <a>430 OWASP Juice Shop431 </a>432 founder and project leader433 <br>434 Niklas Düster,435 <a>436 OWASP Dependency-Track437 </a>438 co-project leader439 <br>440 Jeroen Willemsen,441 <a>442 OWASP WrongSecrets443 </a>444 project leader445 <br>446 Jeremy Long,447 <a>448 OWASP dependency-check449 </a>450 founder and project lead and451 <a>452 OWASP Java Encoder453 </a>454 contributor455 <br>456 Cole Cornford,457 <a>458 OWASP Code Review Guide459 </a>460 project lead and461 <a>462 OWASP XSS Prevention CheatSheet463 </a>464 author465 <br>466 Ben Gittins, OWASP Member and Contributor467 <br>468 Erwin Geirnaert, Creator of the first OWASP WebGoat Solutions Guide, first OWASP Top 10 for Java and part of the OWASP Community since 2000469 <br>470 Robin Wood, OWASP contributor and supporter471 <br>472 Rob Grant, OWASP contributor473 <br>474 Arkaprabha Chakraborty, OWASP contributor and475 <a>476 OWASP ZAP477 </a>478 extended team member479 <br>480 Curtis Koenig, Founding member OWASP Louisville, Former Chapter Leader OWASP Louisville, OWASP Member481 <br>482 Cláudio André,483 <a>484 OWASP MASTG485 </a>486 Top Contributer487 <br>488 István Albert-Tóth,489 <a>490 OWASP CSRFGuard491 </a>492 project co-lead493 <br>494 Katie Paxton-Fear, educational web security YouTuber495 <br>496 Jakub Maćkowski, OWASP contributor and497 <a>498 OWASP Cheat Sheet Series499 </a>500 co-project leader501 <br>502 Somdev Sangwan, Open Source Security Tools Developer503 <br>504 Edoardo Ottavianelli, Open Source Security Tools Developer505 <br>506 Aram Hovsepyan,507 <a>508 OWASP SAMM509 </a>510 core team member511 <br>512 Brian Glas,513 <a>514 OWASP Top 10515 </a>516 Co-Lead,517 <a>518 OWASP SAMM519 </a>520 Core team member, OWASP SAMM Benchmark Co-Lead521 <br>522 Jeff Williams, OWASP Chair from 2001-2011, Creator of OWASP Top Ten, WebGoat, ESAPI, ASVS, XSS Prevention Cheatsheet, OWASP Legal, Chapters Program, OWASP Foundation, the OWASP Wiki, and more523 <br>524 Dimitar Raichev,525 <a>526 OWASP SAMM527 </a>528 contributor & tool developer529 <br>530 Dinis Cruz, Past OWASP Board member, organiser of multiple OWASP Conferences and Summits, lead multiple OWASP projects and chapters531 <br>532 Sachin Kumar Dhaka, OWASP Jaipur Member and Budding Security Researcher533 <br>534 Jessy Ayala, OWASP Member and Contributor535 <br>536 Paul McCann,537 <a>538 OWASP Security Shepherd539 </a>540 maintainer and contributor541 <br>542 Karan Preet Singh Sasan,543 <a>544 Owasp VulnerableApp545 </a>546 project leader and547 <a>548 OWASP ZAP549 </a>550 extended team member551 <br>552 Daniel Wood, OWASP Lifetime Member553 <br>554 Bharath, OWASP (Bangalore Chapter) Member and Contributor555 <br>556 John Viega, original OWASP advisory board member, OWASP Lifetime Member557 <br>558 Carol Valencia, Security cloud-native and open-source enthusiast559 <br>560 Jimmy Mesta,561 <a>562 OWASP Kubernetes Top Ten563 </a>564 Project Leader and Cheatsheet Contributor565 <br>566 Lewis Ardern,567 <a>568 OWASP Bay Area Chapter Leader (2019-2022)569 </a>570 , and created the571 <a>572 What is OWASP?573 </a>574 Video575 <br>576 Alvin Smith,577 <a>578 OWASP Juice Shop579 </a>580 Contributor581 <br>582 Sven Schleier,583 <a>584 OWASP Mobile Application Security585 </a>586 , Co-Project Leader of OWASP MASVS and MASTG587 <br>588 Carlos Holguera,589 <a>590 OWASP Mobile Application Security591 </a>592 , Co-Project Leader of OWASP MASVS and MASTG593 <br>594 Jeroen Beckers,595 <a>596 OWASP Mobile Application Security597 </a>598 , Co-Author of OWASP MASVS and MASTG599 <br>600 Shubham Palriwala,601 <a>602 OWASP Juice Shop603 </a>604 Core Team member605 <br>606 Pinaki Mondal, Open Source Security Tools Developer607 <br>608 Zsolt Imre, CTO at private company609 <br>610 Eoin Keary, Former OWASP Global Board Vice Chair (2010-2015), Former Testing and Code Review Guide lead611 <br>612 Deepayan Chanda, Principal Cybersecurity Architect613 <br>614 Martín Marsicano, OWASP Lifetime Member, Former Chapter Leader OWASP Uruguay and several projects contributor615 <br>616 Paul Schwarzenberger,617 <a>618 OWASP Domain Protect619 </a>620 creator and project leader621 <br>622 Abraham Aranguren,623 <a>624 OWASP OWTF Project625 </a>626 creator and project leader627 <br>628 Viyat Bhalodia,629 <a>630 OWASP OWTF Project631 </a>632 project leader633 <br>634 Dave Ferguson, Project contributor and former chapter leader635 <br>636 Josh Larsen, OWASP Lifetime Member637 <br>638 Sergey Pronin, Principal Security Architect, OWASP Lifetime Member639 <br>640 James, BugBounter, Pentester and OWASP passionate641 <br>642 Kevin W. Wall,643 <a>644 OWASP ESAPI645 </a>646 project co-lead, OWASP Lifetime Member, and647 <a>648 OWASP ZAP649 </a>650 and651 <a>652 OWASP Cheat Sheets Series653 </a>654 contributor655 <br>656 Cesar Kohl,657 <a>658 OWASP ASVS659 </a>660 and661 <a>662 OWASP Cheat Sheets Series663 </a>664 contributor665 <br>666 Simon Whittaker, OWASP Lifetime Member667 <br>668 Frank Catucci, CTO and Head of Security Research at Invicti, OWASP Member and former OWASP Chapter Leader669 <br>670 Ingo Struck, Former OWASP Leader, creator of the name671 <a>672 WebGoat673 </a>674 , OWASP Lifetime Member675 <br>676 Francesco Maria Ferazza, Director of IT, security lecturer and researcher677 <br>678 Antonio Montillo, OWASP enthusiast679 <br>680 Daniel Neagaru,681 <a>682 OWASP Raider683 </a>684 project leader685 <br>686 Rejah Rehim,687 <a>688 OWASP Kerala689 </a>690 Chapter leader691 <br>692 Grant Ongers, OWASP Lifetime Member,693 <a>694 OWASP Cornucopia695 </a>696 and697 <a>698 OWASP Application Security Curriculum699 </a>700 project co-lead701 <br>702 Patrick Reijnders, CISO, OWASP enthusiast; started using the Top Ten as a developer in 2004, now using it as a guideline for pentesting.703 <br>704 Jordan Pike, OWASP Member705 <br>706 Riotaro Okada, OWASP Lifetime member, OWASP Projects contributer, an OWASP Japan chapter lead707 <br>708 Magno Logan, OWASP Member since 2011, former709 <a>710 OWASP Paraiba Chapter Leader711 </a>712 2011-2016,713 <a>714 OWASP Paraiba Day 2012715 </a>716 Organizer, OWASP Portuguese Language Project contributor and717 <a>718 OWASP Top 10 Java EE719 </a>720 translator721 <br>722 Steven van der Baan, OWASP Member and OWASP Cambridge co-lead723 <br>724 David Hunt, OWASP Member and OWASP Columbus co-lead725 <br>726 Mauricio Harley, OWASP Member, former OWASP Fortaleza chapter founder and leader, OWASP MSTG/MASVS contributor727 <br>728 Wael Ghandour, OWASP Member729 <br>730 Yevgeniy Goncharov, Open Source Security Tools Developer731 <br>732 </p>733 <!--734Please:735* Add your name at the end of the list.736* Only link to OWASP projects or chapters737* Do not include any company details738Many thanks739-->740 <hr>741 <p>742 Published on 2023/02/13743 </p>744 <hr>745 <p>746 This “Open Letter to the OWASP Board” is no longer accepting any changes.747 </p>748 </section>749 <footer>750 This page was generated by751 <a>752 GitHub Pages753 </a>754 .755 </footer>756 </div>757 </div>758 </body>759</html>760