creedengo is a collective project aiming to reduce environmental footprint of software at the code level. The goal of the project is to provide a list of static code analyzers to highlight code structures that may have a negative ecological impact: energy and resources over-consumption, "fatware", shortening terminals' lifespan, etc.

creedengo is based on evolving catalogs of good practices, for various technologies. A SonarQube plugin then implements these catalogs as rules for scanning your projects.

Warning: this is still a very early stage project. Any feedback or contribution will be highly appreciated. Please refer to the contribution section.

🌿 SonarQube Plugins

7 technologies are supported by creedengo right now:

• "standard" plugins :
  • Java plugin
  • JavaScript plugin
  • PHP plugin
  • Python plugin
  • C# plugin
• mobile plugins :
  • Android plugin
  • iOS plugin

eco-design SonarQube plugin

There are two kinds of plugins :

• One for web / backoffice (PHP, Python, Java, JavaScript), using smells described in the 2nd edition of the repository published in september 2015. You can find all the rules here (in french). The current repository is for web / backOffice
• One for mobile (Android), using a set of smells theorised by Olivier Le Goaër for Android. You can find this plugin in the repository here

How a SonarQube plugin works

Code is parsed to be transformed as AST. AST will allow you to access one or more nodes of your code. For example, you’ll be able to access of all your for loop, to explore content etc.

To better understand AST structure, you can use the AST Explorer.

creedengo rules specification repository

This project contains the specifications of all creedengo rules, for all languages.

Structure

Rules are organized by folder based on their ID in the root rules folder. Each of these folders contains a file with the metadata of the rule, and description by language.

The metadata file uses the format supported by the SonarSource Analyzers Commons library. To find out what values can be put there, we advise you to use the official SonarQube documentation, and to rely on already existing files.

Here is an example:

src/main/rules
├── EC104
│   ├── java
│   │   ├── EC104.asciidoc
│   │   ├── EC104.json
│   ├── php
│   │   ├── EC104.asciidoc
│   ├── python
│   │   ├── EC104.asciidoc
│   └── EC104.json
├── ...

To specify metadata for a given language (for example deprecate a rule only for a single language), it is possible to create a json file in the language folder, and this will be merged with the common file during build. The keys in the specific file have priority and it is possible to add new ones but not to delete them from the global one.

Description language

The description of the rules uses the ASCIIDOC format ( with Markdown compatibility) in order to allow the inclusion of other pages (this feature is not available in standard with Markdown).

See:

• AsciiDoc Syntax Quick Reference
• Compare AsciiDoc to Markdown

🚀 Getting Started

You can quickly have a look of creedengo plugins with docker. Plase have a look at "Getting started" section of each plugin :

• Java plugin
• PHP plugin
• Python plugin
• C# plugin

🛒 Distribution

The main way to get creedengo plugins is to download them from your SonarQube Marketplace (available in Administration section). But if you want, you can also download them from GitHub releases.

We had split our plugins repository creedengo to one repository for each plugin on december 2023. Thus, plugin versions are available on 2 repositories depending on version you want :

• Java plugin :
  • from 0.x to 1.4.3 : creedengo repository
  • since 1.5.0 : creedengo-java repository
• PHP plugin :
  • from 0.x to 1.3.1 : creedengo repository
  • since 1.4.0 : creedengo-php repository
• Python plugin :
  • from 0.x to 1.3.1 : creedengo repository
  • since 1.4.0 : creedengo-python repository
• Javascript plugin :
  • from 0.x to 1.3.0 : creedengo repository
  • since 1.4.0 : creedengo-javascript repository
• C# plugin :
  • since 0.x : creedengo repository
• Android plugin : creedengo-android repository
• iOS plugin : creedengo-ios repository

🧩 Plugins version compatibility

Plugins Version	SonarQube version
1.4.+	SonarQube 9.4.+ LTS to 10.1
1.3.+	SonarQube 9.4.+ LTS to 10.0
1.2.+	SonarQube 9.4.+ LTS to 10.0
1.1.+	SonarQube 9.4.+ LTS to 9.9
1.0.+	SonarQube 9.4.+ LTS to 9.9
0.2.+	SonarQube 9.4.+ LTS to 9.9
0.1.+	SonarQube 8.9.+ LTS to 9.3

☕ Plugin Java part compatibility

Plugins Version	Java version
1.4.+	11 / 17
1.3.+	11 / 17
1.2.+	11 / 17
1.1.+	11 / 17
1.0.+	11 / 17
0.2.+	11 / 17
0.1.+	11 / 17

🤝 Contribution

You are a technical expert, a designer, a project manager, a CSR expert, an ecodesign expert...

You want to offer the help of your company, help us to organize, communicate on the project ?

You have ideas to submit to us ?

We are listening to you to make the project progress collectively, and maybe with you !

WE NEED YOU !

Here the Starter pack

🤓 Main contributors

Any question ? We are here for you ! first, create an issue, please. Then, if no answer, contact ...

• Jules Delecour
• Geoffrey Lalloué
• Julien Hertout
• Justin Berque
• Olivier Le Goaër
• Maxime DUBOIS
• David DE CARVALHO
• Maxime MALGORN
• Gilles GROUSSET
• Vianney DE BELLABRE
• Jérôme CARDON
• Johanna DUIGOU

🧐 Core Team Emeriti

Here we honor some no-longer-active core team members who have made valuable contributions in the past.

• Gaël Pellevoizin
• Nicolas Daviet
• Mathilde Grapin

They have contributed to the success of creedengo :

• Davidson Consulting
• Orange Business
• Snapp'
• Université de Pau et des Pays de l'Adour (UPPA)
• Solocal / PagesJaunes.fr
• Capgemini
• Accenture

They supported the project :

• Région Nouvelle-Aquitaine

Links

• https://docs.sonarqube.org/latest/analysis/overview/