Add flowR configuration file#391
Conversation
Added a new JSON configuration file for flowR.
|
Sorry, I've just copied the json from the tool. Should I fix this issue using the supplied prettyfier or is this "fine" for tool jsons? |
|
Hi @EagleoutIce I will review it promptly. |
vuillaut
left a comment
vuillaut
left a comment
There was a problem hiding this comment.
Please prettify the json file using the provided prettifier
Co-authored-by: Thomas Vuillaume <thomas.vuillaume@lapp.in2p3.fr>
|
Ok so now I've executed the prettifier (even though I was surprised that pasting the JSON from the "Suggest a new tool" was not prettified already. Additionally, I've reduced the quality indicators to only reflect those we can measure/for which flowR can be used to measure them. |
| { | ||
| "@id": "https://w3id.org/everse/i/indicators/no_leaked_credentials", | ||
| "@type": "@id" | ||
| }, |
There was a problem hiding this comment.
could you provide evidence that flowR can measure that indicator please?
I cannot find any in the documentation.
| { | ||
| "@id": "https://w3id.org/everse/i/indicators/software_has_tests", | ||
| "@type": "@id" | ||
| }, |
There was a problem hiding this comment.
could you provide evidence that flowR can measure that indicator please?
I cannot find any in the documentation.
| { | ||
| "@id": "https://w3id.org/everse/i/indicators/software_has_license", | ||
| "@type": "@id" | ||
| } |
There was a problem hiding this comment.
could you provide evidence that flowR can measure that indicator please?
I cannot find any in the documentation.
Added a new JSON configuration file for flowR.
🆕 Tool
Name: flowR
Repository URL: https://github.com/flowr-analysis/flowr
Checklist
The tool:
Metadata file:
Research Usage Evidence (at least one required)
Provide concrete links:
Links:
Link:
Link:
DOI / link: https://doi.org/10.1016/j.knosys.2026.115412, https://doi.org/10.1145/3691620.3695359, https://doi.org/10.36190/2025.49, https://doi.org/10.1109/WI-IAT62293.2024.00037, ...
If none apply, justify why this tool is relevant for research software.
Active Maintenance
Lifecycle & Applicability
Justification for the research software tier(s) it can be applied to: