Merge pull request #151 from andriumon/pr-code-smells

Add indicator code_smells_ok

Author: dgarijo

indicators/code_smells_ok.json

@@ -0,0 +1,30 @@
+{
+  "@context": "https://w3id.org/everse/rsqi#",
+  "@id": "https://w3id.org/everse/i/indicators/code_smells_ok",
+  "@type": "SoftwareQualityIndicator",
+  "name": "Code smells follow community conventions",
+  "abbreviation": "code_smells_ok",
+  "identifier": { "@id": "https://w3id.org/everse/i/indicators/code_smells_ok" },
+  "description": "The code smell ratio is maintained at a reasonable level according to community standards and conventions. Code smells are indicators of possible design problems mainly for maintainability of the code (i.e. functions too large, code that is how to read, too many input parameters for a function, etc.). The density of code smells can be estimated with the code smell ratio, an estimator of code smells within a codebase of project often meassured using rule-based checks (i.e. Sonarqube). An example for calculating it could be (code_smells/lines_of_code)*1000.",
+  "status": "Active",
+  "keywords": [
+    "maintainability", "quality", "code smell", "code"
+  ],
+  "version": "1.0.0",
+  "contact": [
+    {
+        "@type": "schema:Person",
+        "name": "Daniel Garijo"
+    },
+    {
+        "@type": "schema:Person",
+        "name": "Andres Montero"
+    }
+  ],
+  "source": {
+    "url": "https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=11216562&tag=1",
+    "name": "Socially-Informed Jupyter Notebook Quality: A Role- and Lifecycle-Aware Metrics Framework"
+  },
+  "qualityDimension": { "@id": "https://w3id.org/everse/i/dimensions/maintainability" },
+  "created": "14-04-2026"
+}