Need help with chromium-dashboard?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

418 Stars 294 Forks Apache License 2.0 1.6K Commits 284 Opened issues


Chrome Status Dashboard

Services available


Need anything else?

Contributors list

Chrome Platform Status

Lighthouse score: 100/100

Get the code

git clone --recursive


  1. Install global CLIs
    1. Google App Engine SDK for Python.
    2. pip, node, npm.
    3. Gulp
      npm install -g gulp
  2. Install npm dependencies
    npm ci
  3. Install other dependencies
    npm run deps
    npm run dev-deps
Add env_vars.yaml

Create a file named

in the root directory and fill it with:
  DJANGO_SECRET: 'this-is-a-secret'


To start the main server and the notifier backend, run:

npm start

Then visit


To start front end code watching (sass, js lint check, babel, minify files), run

npm run watch

To run lint & lit-analyzer:

npm run lint

To run unit tests:

npm run test

Note: featurelist is temporarily excluded because lit-analyzer throws

Maximum call stack size exceeded

There are some developing information in


  • If you get an error saying

    No module named protobuf
    , try installing it locally with
    python -m pip install protobuf
  • When installing the GAE SDK, make sure to get the version for python 2.7. It is no longer the default version.

  • When running

    npm start
    you may get an ImportError for jinja2.tests. This was caused by an over-general line in skip_files.yaml. Pulling the latest source code should resolve the problem.

Blink components

Chromestatus gets the list of Blink components from a separate app running on Firebase. See source.

Seed the blink component owners

Visit http://localhost:8080/admin/blink/populate_blink to see the list of Blink component owners.

Debugging / settings
contains a list of globals for debugging and running the site locally.


If you have uncommited local changes, the appengine version name will end with

. It is OK to test on staging with tainted versions, but everything should be committed (and thus not tainted) before staging a version that can later be pushed to prod.

Note you need to have admin privileges on the

cloud projects to be able to deploy the site.

Run the npm target:

npm run staging

Open the Google Developer Console for the staging site and flip to the new version by selecting from the list and clicking MIGRATE TRAFFIC. Make sure to do this for both the 'default' service as well as for the 'notifier' service.

If manual testing on the staging server looks good, then repeat the same steps to deploy to prod:

npm run deploy

Open the Google Developer Console for the production site

The production site should only have versions that match versions on staging.


Copyright (c) 2013-2016 Google Inc. All rights reserved.

Apache2 License.


We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.