All Projects → theodo → tyrion

theodo / tyrion

Licence: other
No description or website provided.

Programming Languages

typescript
32286 projects
javascript
184084 projects - #8 most used programming language
HTML
75241 projects

Projects that are alternatives of or similar to tyrion

Qualinsight Plugins Sonarqube Badges
Plugin for SonarQube that generates badges displaying information about a project's or view's quality.
Stars: ✭ 108 (+30.12%)
Mutual labels:  quality, sonarqube
Sonar Java
☕️ SonarSource Static Analyzer for Java Code Quality and Security
Stars: ✭ 745 (+797.59%)
Mutual labels:  quality, sonarqube
Sonarondocker
🐳 📡 Docker way of running SonarQube + any DB
Stars: ✭ 25 (-69.88%)
Mutual labels:  quality, sonarqube
Zpa
A parser and source code analyzer for PL/SQL and Oracle SQL.
Stars: ✭ 124 (+49.4%)
Mutual labels:  quality, sonarqube
Sonar Cnes Report
Generates analysis reports from SonarQube web API.
Stars: ✭ 145 (+74.7%)
Mutual labels:  quality, sonarqube
sonar-scala
A free and open-source SonarQube plugin for static code analysis of Scala projects.
Stars: ✭ 113 (+36.14%)
Mutual labels:  quality, sonarqube
sbt-sonar
An sbt plugin which provides an easy way to integrate Scala projects with SonarQube.
Stars: ✭ 62 (-25.3%)
Mutual labels:  quality, sonarqube
sonarlint4netbeans
SonarLint integration for Apache Netbeans
Stars: ✭ 23 (-72.29%)
Mutual labels:  quality, sonarqube
CI-CD-Docker
No description or website provided.
Stars: ✭ 21 (-74.7%)
Mutual labels:  sonarqube
sonar-issueresolver-plugin
Export and import resolved issues
Stars: ✭ 12 (-85.54%)
Mutual labels:  sonarqube
python-test-reporter
DEPRECATED Uploads Python test coverage data to Code Climate
Stars: ✭ 18 (-78.31%)
Mutual labels:  quality
sonarqube-action
Integrate SonarQube scanner to GitHub Actions
Stars: ✭ 90 (+8.43%)
Mutual labels:  sonarqube
qamd
QAMyData, a data quality assurance tool for SPSS, STATA, SAS and CSV files.
Stars: ✭ 16 (-80.72%)
Mutual labels:  quality
noise-php
A starter-kit for your PHP project.
Stars: ✭ 52 (-37.35%)
Mutual labels:  sonarqube
sonar-fsharp-plugin
F# SonarQube (TM) plugin - support for F#
Stars: ✭ 46 (-44.58%)
Mutual labels:  sonarqube
symfony-lts-docker-starter
🐳 Dockerized your Symfony project using a complete stack (Makefile, Docker-Compose, CI, bunch of quality insurance tools, tests ...) with a base according to up-to-date components and best practices.
Stars: ✭ 39 (-53.01%)
Mutual labels:  quality
sonar-cobertura
Cobertura plugin for SonarQube
Stars: ✭ 30 (-63.86%)
Mutual labels:  sonarqube
hulks
Olist custom linting hooks 💚 👽
Stars: ✭ 25 (-69.88%)
Mutual labels:  quality
codeclimate-eslint
Code Climate Engine for ESLint
Stars: ✭ 86 (+3.61%)
Mutual labels:  quality
CanAirIO
W A R N I N G: This is a previous proof of concept of CanAirIO device firmware over a TTGO T-Display board, but now it is only a old reference. The last stable version of CanAirIO device already have support for this board and many features more. Please use the official CanAirIO Firmware instead of this firmware. https://github.com/kike-canaries…
Stars: ✭ 12 (-85.54%)
Mutual labels:  quality

Tyrion

CircleCI FOSSA Status NPM Downloads

About the tool

Why this tool

We defined at Theodo quality by the "3S quality factor" that the code:

  • 🐛 Stable : has no bugs and the code is easy to maintain
  • 🚀 Speed: is fast and scalable (speed at scale)
  • 🔒 Secured: is secured

We think that a team needs the following to be able to deliver code of high quality:

  • 📆 Have enough time
  • 🗹 Know how to do quality
  • 🛠️ Have the right tools
  • 🌡️ Be able to measure quality

The goal of tyrion is to help you on the last point "🌡 Be able to measure quality".

Monitoring technical debt

We defined technical debt as every piece of code or architecture that prevents quality. Through various experiments, we saw that when we were monitoring the evolution of the technical debt it was more likely to prevent it to increase. We tried different ways of managing and measuring it in the past (Trello cards, google docs, post-it, ..) but we never found a painless solution that would allow us to:

  • 🔍️ Document and update the debt while coding
  • 📊 Quickly get an overview and the evolution of the debt
  • 👩‍🔧 Have a simple prioritization of the debt

So we created Tyrion. You can now:

  • Document and update your debt directly in the code with specific comments (🔍)
  • Automatically get charts and paretos that help you decide which part of the code you should improve next (📊, 👩‍🔧)

Installation:

You need to use tyrion with node v12 or v14. It is not currently working with superior version mainly because problems with the main tool with use: NodeGit.

Install Tyrion globally: npm i -g tyrionl (yes, tyrionl with a final l, it's not a typo).

Usage:

Run tyrion with the following options

  -p, --path [scanDirectory]  The path of the directory you want to analyse
  -e, --evolution [days]      Get the evolution of the debt since X days
  -b, --branch [days]         Specify the branch used for the evolution analysis. (Default to master)
  -n, --nobrowser [browser]   Don't open the report after being generated
  -c, --csv [csv]             export the debt data into a csv file
  -d, --devs [devs]           Get information about who is contributing the most to quality (Beta)
  -h, --help                  output usage information

Example:

  • tyrion -p ./src -c to get the current debt score and create a csv report
  • tyrion --evolution 28 -p . to get the evolution of the debt during 28 days starting from the last commit.
  • tyrion --evolution 28 -b prod -p . to get the evolution of the debt during 28 days starting from the last commit of the prod branch.

Writing debt comment

You can use either the following debt tag for the same result: @debt, TODO, FIXME.

Tyrion parses the files looking for comments that follows the following convention:

/**
 * @debt DEBT_TYPE:SUB_TYPE
 */

There is a default score for the following DEBT_TYPE:

  • architecture
  • bug
  • bug-risk
  • security
  • security-risk
  • quality
  • test
  • doc
  • ci
  • deploy
  • dev-env

You don't need to specify a SUB_TYPE, so a minimum example can be:

/**
 * @debt quality
 */

You can add a comment to provide more details about the debt item by following this convention:

/**
 * @debt DEBT_TYPE:SUB_TYPE "Author: comment"
 */

A complete example could be:

/**
 * @debt security:sql-injection "Maximet: The request is not escaped when being called from the command"
 */

The parser will look for all lines containing '@debt' and starting either by * or # which should cover most web programing languages.

Override and set the price of each type

You can override the default pricing of debt items by creating a .tyrion-config.json file in the root directory of your project. You can even create your own types. Here is the default one:

{
  "pricer": {
    "bug": 100,
    "architecture": 100,
    "bugRisk": 5,
    "security": 100,
    "securityRisk": 10,
    "quality": 5,
    "test": 5,
    "doc": 3,
    "ci": 30,
    "deploy": 10,
    "devEnv": 10,
    "outdated": 5
  },
  "standard": 100,
  "ignorePath": [
    "node_modules",
    "README.md"
  ],
  "debtTags": [
    "@debt",
    "TODO",
    "FIXME"
  ]
}

Writing good practices examples

You can also mark some files as being "Joconde" a file that follows perfectly the standard of code quality. You can use either the following tag for the same result: @best, @standard, JOCONDE.

Example: // JOCONDE React:component "The standard can be find here: http....."

Ignore paths

You can ignore files containing certain strings by using the "ignorePath" option in the config file:

"ignorePath": [
  "node_modules",
  "README.md"
]

Change default debt tag

You can change the default debt tags used to detect which comment line should be consider as a debt comment by Tyrion. To do so override the debtTags entry in .tyrion-config.json:

  "debtTags": [
    "@debt",
    "TODO",
    "FIXME"
  ]

Filtering [REMOVED]

This function is not available anymore as it wasn't used.

You can filter the result by any type of debt you want with the option --filter. It will compare the type and the string you pass as an argument after filter.

Example: tyrion -p ./src --filter bug

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].