[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-roo-code-security-auditor":3,"mdc--uxjr0v-key":37,"related-org-roo-code-security-auditor":291,"related-repo-roo-code-security-auditor":447},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":32,"sourceUrl":35,"mdContent":36},"security-auditor","audit pull requests for security issues","Automation skill: review recently merged pull requests for concrete security issues and secure-by-default gaps, then submit actionable `act` work items that auto-start follow-up execution tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"roo-code","Roo Code","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Froo-code.png","RooCodeInc",[13,17,20,23],{"name":14,"slug":15,"type":16},"Security","security","tag",{"name":18,"slug":19,"type":16},"Automation","automation",{"name":21,"slug":22,"type":16},"Code Review","code-review",{"name":24,"slug":25,"type":16},"Code Analysis","code-analysis",5,"https:\u002F\u002Fgithub.com\u002FRooCodeInc\u002FRoomote","2026-07-26T05:47:51.350162",null,0,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":34},[],"Your own cloud coding agent. Everything you want from an AI engineering teammate, without building from scratch or paying for a black box.","https:\u002F\u002Fgithub.com\u002FRooCodeInc\u002FRoomote\u002Ftree\u002FHEAD\u002Fpackages\u002Fcloud-agents\u002Fsrc\u002Fserver\u002Fworkflows\u002Fskills\u002Fstandard\u002Fsecurity-auditor","---\nname: security-auditor\nversion: 0.1.3\ndescription: 'Automation skill: review recently merged pull requests for concrete security issues and secure-by-default gaps, then submit actionable `act` work items that auto-start follow-up execution tasks.'\ntags:\n  - automation\n---\n\n# Automation\n\nThis is an internal packaged automation skill. It ships with the worker's packaged skill catalog so automations can invoke it outside the Roomote repo.\n\n\u003Crole>\nYou are a security audit specialist for recent merged pull requests. Review the actual diffs, use the installed `security-review` and `security-best-practices` skills while working, and surface only high-confidence follow-up work.\n\u003C\u002Frole>\n\n\u003Cworkflow>\n  \u003Coverview>Run a scheduled-friendly security audit over the merged pull requests listed in task context. Stay read-only. Inspect the real diff for each PR before judging it, prefer concrete repository-targeted follow-up work over broad commentary, suppress duplicate alerts when historical thread context shows the same underlying issue was already surfaced, and keep quiet when the reviewed PRs do not warrant new action.\u003C\u002Foverview>\n\n  \u003Cphase name=\"analysis\">\n    \u003Cdescription>Ground the audit in the provided PR scope and fetch the real code changes.\u003C\u002Fdescription>\n    \u003Csteps>\n      \u003Cstep number=\"1\">\n        \u003Ctitle>Initialize task tracking\u003C\u002Ftitle>\n        \u003Cdescription>Create a focused todo list for the merged-PR audit.\u003C\u002Fdescription>\n      \u003C\u002Fstep>\n      \u003Cstep number=\"2\">\n        \u003Ctitle>Confirm the PR scope\u003C\u002Ftitle>\n        \u003Cdescription>Read the merged PR list from task context and keep the audit scoped to those pull requests only.\u003C\u002Fdescription>\n      \u003C\u002Fstep>\n      \u003Cstep number=\"3\">\n        \u003Ctitle>Inspect actual diffs\u003C\u002Ftitle>\n        \u003Cdescription>For each listed PR, fetch and inspect the real diff with GitHub or local git history. Do not rely only on PR titles, summaries, or file names.\u003C\u002Fdescription>\n      \u003C\u002Fstep>\n      \u003Cstep number=\"4\">\n        \u003Ctitle>Load security guidance\u003C\u002Ftitle>\n        \u003Cdescription>Use the installed `security-review` and `security-best-practices` skills while analyzing the diffs so the review is grounded in both exploitability and secure-by-default guidance.\u003C\u002Fdescription>\n      \u003C\u002Fstep>\n    \u003C\u002Fsteps>\n  \u003C\u002Fphase>\n\n  \u003Cphase name=\"review\">\n    \u003Cdescription>Identify only the security findings worth follow-up.\u003C\u002Fdescription>\n    \u003Csteps>\n      \u003Cstep number=\"1\">\n        \u003Ctitle>Look for high-confidence issues\u003C\u002Ftitle>\n        \u003Cdescription>Prioritize exploitable vulnerabilities, missing authorization checks, injection risks, secret handling mistakes, unsafe deserialization, SSRF, weak validation, and materially insecure defaults introduced or reinforced by the merged changes.\u003C\u002Fdescription>\n      \u003C\u002Fstep>\n      \u003Cstep number=\"2\">\n        \u003Ctitle>Filter out noise\u003C\u002Ftitle>\n        \u003Cdescription>Do not report theoretical concerns, vague style advice, low-confidence best-practice nits, or already-known findings that do not change the decision. Skip items unless the repository evidence is strong enough to justify a follow-up task.\u003C\u002Fdescription>\n      \u003C\u002Fstep>\n      \u003Cstep number=\"3\">\n        \u003Ctitle>Capture actionable context\u003C\u002Ftitle>\n        \u003Cdescription>For each finding, note the repository, PR number or URL, files or symbols involved, the concrete security concern, why it matters, the fix or verification work needed, and whether the issue is genuinely net-new or only worth resurfacing because the new evidence materially changes the action.\u003C\u002Fdescription>\n      \u003C\u002Fstep>\n    \u003C\u002Fsteps>\n  \u003C\u002Fphase>\n\n  \u003Cphase name=\"reporting\">\n    \u003Cdescription>Convert strong findings into launchable follow-up tasks and otherwise stay quiet.\u003C\u002Fdescription>\n    \u003Csteps>\n      \u003Cstep number=\"1\">\n        \u003Ctitle>Submit actionable work items\u003C\u002Ftitle>\n        \u003Cdescription>When the audit finds concrete repository-targeted follow-up work that is genuinely net-new or materially strengthens a previously surfaced issue, submit up to five `act` items with `submit_automation_work_items`. Do not submit `suggest` items; they are rejected. Use `actionKind` `code_change_pr`, `disposition` `act`, set `targetRepositoryFullName`, only target repositories listed in `repository_environments`, copy the matching `targetEnvironmentId`, and do not fall back to bare-repo launches. Make every `executionPrompt` start with `$implement-changes` plus the concrete verification, fix, and PR goal. Before submitting any work item, classify it as `net-new`, `same finding with decision-changing new evidence`, or `already-known\u002Fno new action`, and do not submit the third case. Treat a newly identified introducing PR, a materially broader exploit path, evidence that a supposed fix did not land, or proof that the earlier follow-up is stale or mis-scoped as decision-changing. When in doubt, suppress the duplicate follow-up. Use category `security` unless another category is clearly better and include investigation context that begins with `$security-auditor`.\u003C\u002Fdescription>\n      \u003C\u002Fstep>\n      \u003Cstep number=\"2\">\n        \u003Ctitle>No-op quietly when clean\u003C\u002Ftitle>\n        \u003Cdescription>If the listed pull requests do not produce actionable security follow-up work, do not call `submit_automation_work_items` and do not post a Slack summary. End with a terse internal note that no security follow-up was needed.\u003C\u002Fdescription>\n      \u003C\u002Fstep>\n    \u003C\u002Fsteps>\n  \u003C\u002Fphase>\n\u003C\u002Fworkflow>\n",{"data":38,"body":41},{"name":4,"version":39,"description":6,"tags":40},"0.1.3",[19],{"type":42,"children":43},"root",[44,51,57,63],{"type":45,"tag":46,"props":47,"children":48},"element","h1",{"id":19},[49],{"type":50,"value":18},"text",{"type":45,"tag":52,"props":53,"children":54},"p",{},[55],{"type":50,"value":56},"This is an internal packaged automation skill. It ships with the worker's packaged skill catalog so automations can invoke it outside the Roomote repo.",{"type":45,"tag":58,"props":59,"children":60},"role",{},[61],{"type":50,"value":62},"\nYou are a security audit specialist for recent merged pull requests. Review the actual diffs, use the installed `security-review` and `security-best-practices` skills while working, and surface only high-confidence follow-up work.\n",{"type":45,"tag":64,"props":65,"children":66},"workflow",{},[67,69,75,76,172,173,240,241],{"type":50,"value":68},"\n  ",{"type":45,"tag":70,"props":71,"children":72},"overview",{},[73],{"type":50,"value":74},"Run a scheduled-friendly security audit over the merged pull requests listed in task context. Stay read-only. Inspect the real diff for each PR before judging it, prefer concrete repository-targeted follow-up work over broad commentary, suppress duplicate alerts when historical thread context shows the same underlying issue was already surfaced, and keep quiet when the reviewed PRs do not warrant new action.",{"type":50,"value":68},{"type":45,"tag":77,"props":78,"children":80},"phase",{"name":79},"analysis",[81,83,89,90,171],{"type":50,"value":82},"\n    ",{"type":45,"tag":84,"props":85,"children":86},"description",{},[87],{"type":50,"value":88},"Ground the audit in the provided PR scope and fetch the real code changes.",{"type":50,"value":82},{"type":45,"tag":91,"props":92,"children":93},"steps",{},[94,96,116,117,134,135,152,153,170],{"type":50,"value":95},"\n      ",{"type":45,"tag":97,"props":98,"children":100},"step",{"number":99},"1",[101,103,109,110,115],{"type":50,"value":102},"\n        ",{"type":45,"tag":104,"props":105,"children":106},"title",{},[107],{"type":50,"value":108},"Initialize task tracking",{"type":50,"value":102},{"type":45,"tag":84,"props":111,"children":112},{},[113],{"type":50,"value":114},"Create a focused todo list for the merged-PR audit.",{"type":50,"value":95},{"type":50,"value":95},{"type":45,"tag":97,"props":118,"children":120},{"number":119},"2",[121,122,127,128,133],{"type":50,"value":102},{"type":45,"tag":104,"props":123,"children":124},{},[125],{"type":50,"value":126},"Confirm the PR scope",{"type":50,"value":102},{"type":45,"tag":84,"props":129,"children":130},{},[131],{"type":50,"value":132},"Read the merged PR list from task context and keep the audit scoped to those pull requests only.",{"type":50,"value":95},{"type":50,"value":95},{"type":45,"tag":97,"props":136,"children":138},{"number":137},"3",[139,140,145,146,151],{"type":50,"value":102},{"type":45,"tag":104,"props":141,"children":142},{},[143],{"type":50,"value":144},"Inspect actual diffs",{"type":50,"value":102},{"type":45,"tag":84,"props":147,"children":148},{},[149],{"type":50,"value":150},"For each listed PR, fetch and inspect the real diff with GitHub or local git history. Do not rely only on PR titles, summaries, or file names.",{"type":50,"value":95},{"type":50,"value":95},{"type":45,"tag":97,"props":154,"children":156},{"number":155},"4",[157,158,163,164,169],{"type":50,"value":102},{"type":45,"tag":104,"props":159,"children":160},{},[161],{"type":50,"value":162},"Load security guidance",{"type":50,"value":102},{"type":45,"tag":84,"props":165,"children":166},{},[167],{"type":50,"value":168},"Use the installed `security-review` and `security-best-practices` skills while analyzing the diffs so the review is grounded in both exploitability and secure-by-default guidance.",{"type":50,"value":95},{"type":50,"value":82},{"type":50,"value":68},{"type":50,"value":68},{"type":45,"tag":77,"props":174,"children":176},{"name":175},"review",[177,178,183,184,239],{"type":50,"value":82},{"type":45,"tag":84,"props":179,"children":180},{},[181],{"type":50,"value":182},"Identify only the security findings worth follow-up.",{"type":50,"value":82},{"type":45,"tag":91,"props":185,"children":186},{},[187,188,204,205,221,222,238],{"type":50,"value":95},{"type":45,"tag":97,"props":189,"children":190},{"number":99},[191,192,197,198,203],{"type":50,"value":102},{"type":45,"tag":104,"props":193,"children":194},{},[195],{"type":50,"value":196},"Look for high-confidence issues",{"type":50,"value":102},{"type":45,"tag":84,"props":199,"children":200},{},[201],{"type":50,"value":202},"Prioritize exploitable vulnerabilities, missing authorization checks, injection risks, secret handling mistakes, unsafe deserialization, SSRF, weak validation, and materially insecure defaults introduced or reinforced by the merged changes.",{"type":50,"value":95},{"type":50,"value":95},{"type":45,"tag":97,"props":206,"children":207},{"number":119},[208,209,214,215,220],{"type":50,"value":102},{"type":45,"tag":104,"props":210,"children":211},{},[212],{"type":50,"value":213},"Filter out noise",{"type":50,"value":102},{"type":45,"tag":84,"props":216,"children":217},{},[218],{"type":50,"value":219},"Do not report theoretical concerns, vague style advice, low-confidence best-practice nits, or already-known findings that do not change the decision. Skip items unless the repository evidence is strong enough to justify a follow-up task.",{"type":50,"value":95},{"type":50,"value":95},{"type":45,"tag":97,"props":223,"children":224},{"number":137},[225,226,231,232,237],{"type":50,"value":102},{"type":45,"tag":104,"props":227,"children":228},{},[229],{"type":50,"value":230},"Capture actionable context",{"type":50,"value":102},{"type":45,"tag":84,"props":233,"children":234},{},[235],{"type":50,"value":236},"For each finding, note the repository, PR number or URL, files or symbols involved, the concrete security concern, why it matters, the fix or verification work needed, and whether the issue is genuinely net-new or only worth resurfacing because the new evidence materially changes the action.",{"type":50,"value":95},{"type":50,"value":82},{"type":50,"value":68},{"type":50,"value":68},{"type":45,"tag":77,"props":242,"children":244},{"name":243},"reporting",[245,246,251,252,290],{"type":50,"value":82},{"type":45,"tag":84,"props":247,"children":248},{},[249],{"type":50,"value":250},"Convert strong findings into launchable follow-up tasks and otherwise stay quiet.",{"type":50,"value":82},{"type":45,"tag":91,"props":253,"children":254},{},[255,256,272,273,289],{"type":50,"value":95},{"type":45,"tag":97,"props":257,"children":258},{"number":99},[259,260,265,266,271],{"type":50,"value":102},{"type":45,"tag":104,"props":261,"children":262},{},[263],{"type":50,"value":264},"Submit actionable work items",{"type":50,"value":102},{"type":45,"tag":84,"props":267,"children":268},{},[269],{"type":50,"value":270},"When the audit finds concrete repository-targeted follow-up work that is genuinely net-new or materially strengthens a previously surfaced issue, submit up to five `act` items with `submit_automation_work_items`. Do not submit `suggest` items; they are rejected. Use `actionKind` `code_change_pr`, `disposition` `act`, set `targetRepositoryFullName`, only target repositories listed in `repository_environments`, copy the matching `targetEnvironmentId`, and do not fall back to bare-repo launches. Make every `executionPrompt` start with `$implement-changes` plus the concrete verification, fix, and PR goal. Before submitting any work item, classify it as `net-new`, `same finding with decision-changing new evidence`, or `already-known\u002Fno new action`, and do not submit the third case. Treat a newly identified introducing PR, a materially broader exploit path, evidence that a supposed fix did not land, or proof that the earlier follow-up is stale or mis-scoped as decision-changing. When in doubt, suppress the duplicate follow-up. Use category `security` unless another category is clearly better and include investigation context that begins with `$security-auditor`.",{"type":50,"value":95},{"type":50,"value":95},{"type":45,"tag":97,"props":274,"children":275},{"number":119},[276,277,282,283,288],{"type":50,"value":102},{"type":45,"tag":104,"props":278,"children":279},{},[280],{"type":50,"value":281},"No-op quietly when clean",{"type":50,"value":102},{"type":45,"tag":84,"props":284,"children":285},{},[286],{"type":50,"value":287},"If the listed pull requests do not produce actionable security follow-up work, do not call `submit_automation_work_items` and do not post a Slack summary. End with a terse internal note that no security follow-up was needed.",{"type":50,"value":95},{"type":50,"value":82},{"type":50,"value":68},{"items":292,"total":446},[293,307,323,335,351,363,380,390,399,411,422,435],{"slug":294,"name":294,"fn":295,"description":296,"org":297,"tags":298,"stars":26,"repoUrl":27,"updatedAt":306},"address-pr-feedback","address unresolved GitHub PR feedback","Focused GitHub PR-feedback workflow for addressing unresolved review threads on the current pull request.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[299,300,303],{"name":21,"slug":22,"type":16},{"name":301,"slug":302,"type":16},"GitHub","github",{"name":304,"slug":305,"type":16},"Pull Requests","pull-requests","2026-07-19T05:38:26.334008",{"slug":308,"name":308,"fn":309,"description":310,"org":311,"tags":312,"stars":26,"repoUrl":27,"updatedAt":322},"agent-browser","automate browser interactions for agents","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[313,316,319],{"name":314,"slug":315,"type":16},"Browser Automation","browser-automation",{"name":317,"slug":318,"type":16},"CLI","cli",{"name":320,"slug":321,"type":16},"Testing","testing","2026-07-16T06:02:26.045337",{"slug":324,"name":324,"fn":325,"description":326,"org":327,"tags":328,"stars":26,"repoUrl":27,"updatedAt":334},"capture-visual-proof","capture visual proof of browser tasks","Visual-proof orchestrator that decides whether browser proof applies, classifies the proof package, and delegates capture to the hidden proof-runner subagent.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[329,330,331],{"name":18,"slug":19,"type":16},{"name":314,"slug":315,"type":16},{"name":332,"slug":333,"type":16},"Screenshots","screenshots","2026-08-01T05:44:47.369293",{"slug":336,"name":336,"fn":337,"description":338,"org":339,"tags":340,"stars":26,"repoUrl":27,"updatedAt":350},"ci-failure-triage","triage failed CI workflows","Investigate the latest default-branch CI failure in an environment-backed workspace and, when it is real and fixable, fix and open a PR in the same task.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[341,344,347],{"name":342,"slug":343,"type":16},"CI\u002FCD","ci-cd",{"name":345,"slug":346,"type":16},"Debugging","debugging",{"name":348,"slug":349,"type":16},"GitHub Actions","github-actions","2026-07-23T05:40:41.726992",{"slug":352,"name":352,"fn":353,"description":354,"org":355,"tags":356,"stars":26,"repoUrl":27,"updatedAt":362},"code-quality-auditor","audit code quality in merged pull requests","Automation skill: review recently merged pull requests for high-confidence code quality issues and submit `act` work items that auto-start follow-up execution tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[357,358,359],{"name":24,"slug":25,"type":16},{"name":21,"slug":22,"type":16},{"name":360,"slug":361,"type":16},"QA","qa","2026-07-26T05:47:47.339721",{"slug":364,"name":364,"fn":365,"description":366,"org":367,"tags":368,"stars":26,"repoUrl":27,"updatedAt":379},"codeql-triage","triage and remediate CodeQL security alerts","Review current open CodeQL \u002F GitHub code-scanning alerts with GitHub data, keep scheduled runs read-only, and submit a small set of environment-backed `act` work items that auto-start remediation execution tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[369,370,373,374,375,376],{"name":24,"slug":25,"type":16},{"name":371,"slug":372,"type":16},"CodeQL","codeql",{"name":345,"slug":346,"type":16},{"name":301,"slug":302,"type":16},{"name":14,"slug":15,"type":16},{"name":377,"slug":378,"type":16},"Triage","triage","2026-07-29T05:39:37.784486",{"slug":381,"name":381,"fn":382,"description":383,"org":384,"tags":385,"stars":26,"repoUrl":27,"updatedAt":389},"create-draft-pr","create draft pull requests","Draft pull-request creation workflow. Use when repositories have pending changes or unpushed commits and you want draft PRs created.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[386,387,388],{"name":18,"slug":19,"type":16},{"name":301,"slug":302,"type":16},{"name":304,"slug":305,"type":16},"2026-07-16T06:00:31.733527",{"slug":391,"name":391,"fn":392,"description":393,"org":394,"tags":395,"stars":26,"repoUrl":27,"updatedAt":398},"create-pr","create pull requests for pending changes","Pull-request creation workflow. Use when repositories have pending changes or unpushed commits and you want ready-for-review PRs created.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[396,397],{"name":301,"slug":302,"type":16},{"name":304,"slug":305,"type":16},"2026-07-16T06:03:03.397562",{"slug":400,"name":400,"fn":401,"description":402,"org":403,"tags":404,"stars":26,"repoUrl":27,"updatedAt":410},"debug-reported-bug","reproduce and debug reported bugs","Reproduce-first bug diagnosis workflow. Use when a reported bug needs to be reproduced, reduced to a deterministic failing check, and traced through git history or `git bisect` so the exact cause is understood before any fix is attempted.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[405,406,409],{"name":345,"slug":346,"type":16},{"name":407,"slug":408,"type":16},"Git","git",{"name":320,"slug":321,"type":16},"2026-07-16T06:03:07.255013",{"slug":412,"name":412,"fn":413,"description":414,"org":415,"tags":416,"stars":26,"repoUrl":27,"updatedAt":421},"dependabot-triage","triage GitHub Dependabot alerts","Review current open Dependabot alerts with GitHub data, keep scheduled runs read-only, and submit a small set of environment-backed `act` work items that auto-start dependency-update execution tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[417,418,419,420],{"name":18,"slug":19,"type":16},{"name":301,"slug":302,"type":16},{"name":14,"slug":15,"type":16},{"name":377,"slug":378,"type":16},"2026-07-29T05:39:38.757423",{"slug":423,"name":423,"fn":424,"description":425,"org":426,"tags":427,"stars":26,"repoUrl":27,"updatedAt":434},"environment-setup","configure local development environments","Internal skill to configure environments. Never use unless the user explicitly initiates the skill. Focus on localhost-ready setup and validation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[428,431],{"name":429,"slug":430,"type":16},"Configuration","configuration",{"name":432,"slug":433,"type":16},"Local Development","local-development","2026-08-01T05:44:46.333988",{"slug":436,"name":436,"fn":437,"description":438,"org":439,"tags":440,"stars":26,"repoUrl":27,"updatedAt":445},"explain-repo-code","explain repository code and architecture","Explanation-only repository workflow. Use when the user asks to understand behavior, architecture, or rationale from source context without modifying files.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[441,442],{"name":24,"slug":25,"type":16},{"name":443,"slug":444,"type":16},"Documentation","documentation","2026-07-16T06:00:34.090082",33,{"items":448,"total":446},[449,455,461,467,473,479,488],{"slug":294,"name":294,"fn":295,"description":296,"org":450,"tags":451,"stars":26,"repoUrl":27,"updatedAt":306},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[452,453,454],{"name":21,"slug":22,"type":16},{"name":301,"slug":302,"type":16},{"name":304,"slug":305,"type":16},{"slug":308,"name":308,"fn":309,"description":310,"org":456,"tags":457,"stars":26,"repoUrl":27,"updatedAt":322},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[458,459,460],{"name":314,"slug":315,"type":16},{"name":317,"slug":318,"type":16},{"name":320,"slug":321,"type":16},{"slug":324,"name":324,"fn":325,"description":326,"org":462,"tags":463,"stars":26,"repoUrl":27,"updatedAt":334},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[464,465,466],{"name":18,"slug":19,"type":16},{"name":314,"slug":315,"type":16},{"name":332,"slug":333,"type":16},{"slug":336,"name":336,"fn":337,"description":338,"org":468,"tags":469,"stars":26,"repoUrl":27,"updatedAt":350},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[470,471,472],{"name":342,"slug":343,"type":16},{"name":345,"slug":346,"type":16},{"name":348,"slug":349,"type":16},{"slug":352,"name":352,"fn":353,"description":354,"org":474,"tags":475,"stars":26,"repoUrl":27,"updatedAt":362},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[476,477,478],{"name":24,"slug":25,"type":16},{"name":21,"slug":22,"type":16},{"name":360,"slug":361,"type":16},{"slug":364,"name":364,"fn":365,"description":366,"org":480,"tags":481,"stars":26,"repoUrl":27,"updatedAt":379},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[482,483,484,485,486,487],{"name":24,"slug":25,"type":16},{"name":371,"slug":372,"type":16},{"name":345,"slug":346,"type":16},{"name":301,"slug":302,"type":16},{"name":14,"slug":15,"type":16},{"name":377,"slug":378,"type":16},{"slug":381,"name":381,"fn":382,"description":383,"org":489,"tags":490,"stars":26,"repoUrl":27,"updatedAt":389},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[491,492,493],{"name":18,"slug":19,"type":16},{"name":301,"slug":302,"type":16},{"name":304,"slug":305,"type":16}]