Skip to main content
Projects is the console’s home page. It lists every project in your account with its code reviews, its verification runs and its code wiki. A project is one of:
  • a GitHub repository. Installing the IronBee GitHub App makes every repository it covers a project
  • a GitLab repository. In a connected GitLab group, each repository you pick becomes a project, named by its path after the group with / as -: acme/platform/backend is platform-backend
  • a Bitbucket repository. In a connected Bitbucket workspace, each repository you pick becomes a project, named by its slug: acme/shop is shop
  • a Vercel project or a Netlify site that an owner or admin enabled from Integrations
  • a CLI project: the name your IronBee CLI reports under. A CLI checkout of a github.com, gitlab.com or bitbucket.org repository reports to that repository’s GitHub, GitLab or Bitbucket project instead
Click a project to open its Code review tab. Its other tabs are Code wiki, Code security, Verifications, Scenarios and Settings. Only owners and admins see Code security.

Not active projects

A project that’s no longer enabled on its provider is listed last, under the Not active band. Its card says Deployments are not verified and has a Settings button.
  • For a Vercel project, a Netlify site, or a GitLab or Bitbucket repository, enable it again from the provider’s integration.
  • For a GitHub repository, enable it again from the GitHub integration, or add the repository back to the App on GitHub if it left the App’s repositories.
Projects page in card view with a GitHub project, then the Not active band with a Netlify project whose card says Deployments are not verified Projects page in card view with a GitHub project, then the Not active band with a Netlify project whose card says Deployments are not verified Archived projects aren’t listed here. Owners and admins find them under Settings > Archived projects. See Project settings.

Date range

The date filter in the page header sets the window every number on the page covers. The subtitle shows it as Showing data for a date range.
  • Pick Last 24 Hours, Last 7 Days, Last 30 Days or Last 90 Days.
  • Or pick a Custom Range with a From and To time down to the hour.

Card view

Projects page header with the sort, view toggle, New project and date filter, above a new Bitbucket project card whose Verifications row offers Install the IronBee Pipe, and a Vercel project card whose Code review and Code wiki rows read GitHub, GitLab and Bitbucket only Projects page header with the sort, view toggle, New project and date filter, above a new Bitbucket project card whose Verifications row offers Install the IronBee Pipe, and a Vercel project card whose Code review and Code wiki rows read GitHub, GitLab and Bitbucket only Each project card shows:
  • The header: the provider’s logo, the project’s name and where it lives. A GitHub, GitLab or Bitbucket project shows its repository, such as GitHub · acme/shop, GitLab · acme/platform/backend or Bitbucket · acme/storefront. A Vercel or Netlify project shows its verification type, such as Vercel · Web. On the right, the card shows when the project was last active, when it was created if it hasn’t run yet, or nothing in this window. The menu offers Project settings and, for a GitHub, GitLab or Bitbucket project, Open on GitHub, Open on GitLab or Open on Bitbucket.
  • Code review: the open findings, with critical and high named, such as 1 critical · 1 high open, or No open findings. While a review runs, the row says Reviewing #N. The bars below count the pull requests reviewed in each slice of the window, by their state now: open, merged and closed. Click the row to open the project’s pull requests, or click a bar to open the pull requests of that slice.
  • Verifications: the pass rate and the latest result, such as 92% · passed 2h ago, or Running with the run’s name while a run is in progress. The bars below count the runs in each slice of the window, with how many failed. Click the row to open the project’s verifications, or click a bar to open that run or the runs in that slice.
  • Code wiki: how many pages the wiki has and when it was built, such as 38 pages · built 3h ago, or where it stands: Writing the first version, Refreshing, Not built yet, The first version failed or Off. When a later rebuild failed, the line adds refresh failed after the page count.
Some rows say why there’s nothing to show yet:

List view

Switch to the list with the toolbar’s view toggle. Projects list view with the Project, Provider, Code Review, Runs, Success Rate, Verifications, Fixes, Last Run, Code Wiki and Last Active columns Projects list view with the Project, Provider, Code Review, Runs, Success Rate, Verifications, Fixes, Last Run, Code Wiki and Last Active columns The list has these columns: Click Project, Success Rate, Verifications, Fixes or Last Active to sort. In card view, the sort menu offers Project Name, Success Rate, Verifications, Fixes and Last Activity. The view you pick lasts until you reload the page. To change the default view, open Settings > Visual and set Default View. On a phone, projects always show as cards.
Press ⌘K (or Ctrl+K), or click Search projects or anything… in the top bar.
  • Type at least 3 characters to find a project by name. Picking one opens its Code review tab.
  • With an empty query, the palette shows your Recent projects and the Go to Projects shortcut.
For queries across sessions, verifications, fixes and more, use Search.

Create a project

GitHub, GitLab and Bitbucket repositories don’t need this step. Installing the IronBee GitHub App makes every repository it covers a project, and in a connected GitLab group or Bitbucket workspace, each repository you pick becomes one. If you’ve connected a GitLab group or a Bitbucket workspace but picked no repository yet, the empty Projects page says so and offers Pick repositories, which opens the integration. To add a Vercel project or a Netlify site, an owner or admin clicks New project in the page header:
  1. Under Where does it deploy?, pick a connected Vercel team or Netlify team. Click Continue.
  2. Select what to verify. New projects lists what isn’t a project yet. Enable again lists Not active projects, which come back with their history and settings.
  3. Set each project’s verification type: Web, API or None. None starts nothing on a deployment until you set a type in the project’s settings.
  4. Click Create N projects, Enable N projects, or Create N, enable N when you picked both.
New project dialog for a Vercel team, with two of its five projects selected, each with a Web, API or None choice, and the Create 2 projects button New project dialog for a Vercel team, with two of its five projects selected, each with a Web, API or None choice, and the Create 2 projects button For Vercel, the dialog reminds you that protected preview deployments need a Bypass token secret. Add it in the new project’s Secrets once the project exists. Projects from the CLI are created automatically the first time the CLI reports under a new name.

What’s next?

Verifications

Every verification run of a project.

Project settings

Verification type, environments, variables, secrets and archiving.