Basic GitHub Actions used in dashlord workflows.
| Action | Usage |
|---|---|
| 404 | Check 404 on some URL |
| check-url | Check the existence of given URL |
| declaration-a11y | Verify accessibility mention |
| declaration-rgpd | Check legal mentions, GCU, confidentiality policy |
| dsfr | Check if DSFR is used |
| ecoindex | Compute webpage ecoscore with ecoindex-cli |
| get-html | Get raw HTML of any webpage |
| init | Read dashloard.yml |
| init-from-txt | Read multiple URLs from a text file |
| lhci | Collect LightHouse information |
| report | Build a report.json and a website from latest scans |
| save | Save a single url scan result for dashlord |
| sonarcloud | Extract quality metrics from sonarcloud API |
| tracking | Check the tracking service |
| trivy | Run trivy docker images scanner |
| trivy-ghcr | Run trivy docker images scanner |
| updown-init | Create missing entries in updown.io |
And many more !
DashLord use GitHub Actions to collect data from different tools and store the results in GIT.
Once all URLs have been scanned, the report action generates a report.json and a web report which are commited to GIT.
cd report/www
yarn
yarn startThis will add report.json, config.json, trends.json in report/www/src
based on the content of DASHLORD_REPO_PATH :
DASHLORD_URLS=http://test1.com,http://test1.com \ # optional
DASHLORD_REPO_PATH=/path/to/some/dashlord-repo \ #optional
node report/src # this will create fresh config.json, report.json and trends.json for the websiteSee also the report README
- create a GitHub action that can produce some JSON in your
scans/myaction.json - In
report/src/generateUrlReport, import the minimum from your action JSON to serve it to the frontend via the generatedreport.json - In
report/src/summary, add compute logic for your scanner score. - Build a new report.json, see above
- Run
yarn startin thereport/wwwfolder to start adding types from your action and UI for your component
