{"id":13561625,"url":"https://github.com/bentolor/idea-cli-inspector","last_synced_at":"2026-01-16T07:06:12.005Z","repository":{"id":145807613,"uuid":"47414515","full_name":"bentolor/idea-cli-inspector","owner":"bentolor","description":"A little command-line tool to integrate the awesome IntelliJ IDEA code inspections in your continuous integration (CI) process using Jenkins, Bamboo, et. al.","archived":false,"fork":false,"pushed_at":"2021-07-19T17:43:09.000Z","size":186,"stargazers_count":140,"open_issues_count":3,"forks_count":13,"subscribers_count":4,"default_branch":"master","last_synced_at":"2024-11-04T13:37:49.630Z","etag":null,"topics":["androidstudio","bamboo","ci","codeanalysis","codeanalyzer","codequality","intellij","intellij-ide","travis-ci"],"latest_commit_sha":null,"homepage":null,"language":"Groovy","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/bentolor.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGES.md","contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null}},"created_at":"2015-12-04T16:10:07.000Z","updated_at":"2024-09-28T09:31:41.000Z","dependencies_parsed_at":"2024-01-14T03:36:54.426Z","dependency_job_id":"626348a4-ef05-4a84-b4c9-342ae643ccac","html_url":"https://github.com/bentolor/idea-cli-inspector","commit_stats":null,"previous_names":[],"tags_count":16,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bentolor%2Fidea-cli-inspector","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bentolor%2Fidea-cli-inspector/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bentolor%2Fidea-cli-inspector/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bentolor%2Fidea-cli-inspector/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/bentolor","download_url":"https://codeload.github.com/bentolor/idea-cli-inspector/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247046912,"owners_count":20874737,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["androidstudio","bamboo","ci","codeanalysis","codeanalyzer","codequality","intellij","intellij-ide","travis-ci"],"created_at":"2024-08-01T13:00:59.291Z","updated_at":"2026-01-16T07:06:06.966Z","avatar_url":"https://github.com/bentolor.png","language":"Groovy","readme":"A little command-line tool to integrate the awesome IntelliJ IDEA code\ninspections in your continuous integration (CI) process using Jenkins,\nBamboo, et. al.\n\n# Quick start (using Docker and Maven)\n\n1.  Add a valid IDEA inspection profile file to your project (find them\n    at `.idea/inspectionProfiles`)\n\n2.  Run within your project directory:\n\n\u003cdiv class=\"informalexample\"\u003e\n\n    docker run --rm -v $(pwd):/project bentolor/idea-cli-inspector -rf pom.xml -p inspectionprofile.xml\n\n\u003c/div\u003e\n\nOptionally you can also\n\n  - Use/Add a complete IDEA configuration (`.idea`) to your project.\n    This allows more fine control (i.e. defining inspection scopes)\n\n  - add a `.ideainspect` to control i.e. ignored files/inspections and\n    other details. See the example file provided with\n    idea-cli-inspector.\n\n# Why this tool?\n\nIntelliJ IDEA offers a vast amount of very high-quality, built-in code\ninspections. Currently it has more than 1073 inspections to offer. Using\nproject-shared inspection profiles it’s possible **to guide developers**\nin a wide range of coding aspects in a **non-annoying way**.\n\nIn contrast to well-known quality tools like\n[SonarQube](http://www.sonarqube.org/) these inspections do have quite a\nfew benefits:\n\n  - **violations are instantly visible** during code writing with freely\n    configurable severities and warning levels. (i.e. bold red errors,\n    yellow warning or discreet hints as recommendation)\n\n  - **false alarms can be easily and immediately suppressed.** A simple\n    Alt-Enter directly at the location where they occur is enough.\n    Alternatively you can adjust your inspection settings just\n    on-the-fly (i.e. reduce level, disable inspection or configure\n    inspection properties)\n\n  - IDEA allows you to **check for new violations introduced with your\n    changes** *while you are trying to commit them*\n\n  - Many inspections in IDEA provide semi-automatic quickfixes and\n    auto-corrections. So again sometimes addressing an issue is as\n    simply as pressing Alt-Enter Right arrow Enter.\n\n  - Because all inspections are based on IDEA´s Psi engine (which is a\n    sort of permanent running syntax compiler) the inspections\n    effectively work on an actual AST. So IDEA *understands* the code\n    and does not only look for (textual) patterns which in return leads\n    to a **significantly lower rate of false-positives.**\n\nNevertheless, though IDEA offers on-the-fly analysis and error\nvisualization it does not stop the developer in committing code\nviolating these helpful guidelines into the project repository.\nJetBrain´s CI solution [TeamCity](https://www.jetbrains.com/teamcity/)\ndoes offer a easy and good integration. It is also possible to execute\nthe IDEA project inspection [on the command\nline](https://www.jetbrains.com/idea/help/working-with-intellij-idea-features-from-command-line.html),\nwhich will produce a hard-readable set of XML files and no further\nsupport for integrating this into an automated tool chain.\n\nTherefore I did hack this little Groovy script to easily include \u0026\nreport inspection checks into your CI chain.\n\n# What it does\n\nThis tool is aimed to simplify the inclusion of IDEA code inspection in\nyour CI chain. It executes a command-line based run of an IntelliJ\ninspection run. This produces a set of hardly human-readable XML files\nin the target directory.\n\nTherefore the tool subsequently parses the generated inspection result\nfiles, allows to filter out selected result files and looks for messages\nwith given severity (WARNING and ERROR by default).\n\nThe tool will list issues in a humand-readable form and exit with return\ncode 1 if it did find any issues (your CI tool should interpret this as\nfailure) or will happily tell you that everyhing is fine.\n\n# Prerequisites \u0026 Limitations\n\nThe script is developed in Groovy, so this has to be installed.\nFurthermore you need a valid installation of IntelliJ IDEA.\n\n\u003cdiv class=\"note\"\u003e\n\nDue to a limitation of IDEA itself it is not possible to run more than\none IDEA instance at the same time. Therefore you must ensure, that no\nother IDEA is running on your PC / on your CI agents.\n\n\u003c/div\u003e\n\n# Usage\n\n## Configuration file base usage\n\nIDEA CLI Inspector supports configuration via a `.ideainspect` file in\nthe project root directory. Below is a example:\n\n    # Levels to look for. Default: WARNING,ERROR\n    #levels: WARNING,ERROR,INFO\n\n    # Apply an \"Custom scope\" for the analysis run\n    # This is _the prefered way_ to limit your inspection run to a part of your project files\n    # as it takes effect within IDEA itself.\n    # See: https://www.jetbrains.com/help/idea/2016.2/specify-inspection-scope-dialog.html\n    #\n    # HOWTO:\n    # 1) Create a new scope excluding undesired folders/files (node_modules, doc, ...)\n    # 2) Share the .idea/scopes/scopename.xml with the project\n    # 3) Use the _name_ of the scope (not the file).\n    # 4) Stick to a single word for best compability\n    scope: inspector-code\n\n    # Inspection result files to skip. For example \"TodoComment\" or \"TodoComment.xml\".\n    #\n    # NOTE: This does not have an effect on which inspections are effectively run by IDEA!\n    #       For the sake of performance better disable these inspections within your\n    #       inspection profile. This here is a last-resort mechanism if you want them\n    #       to appear in your IDE but not your CI process\n    #skip: TodoComment,Annotator\n    skip: GroovyAssignabilityCheck\n\n    # Ignore issues affecting source files matching given regex. Example \".*/generated/.*\".\n    #\n    # NOTE: This does not have an effect on the places IDEA looks. Therefore please prefer\n    #       declaring an \"scope\" and exclude those locations via the IDEA scoping mechanism\n    #       for the sake of performance.\n    #       This here is a last-resort mechanism if you have no other options to supress\n    #       specific places/warning.\n    #skipfile: .*/generated/.*,src/main/Foo.java\n\n    # Target directory to place the IDEA inspection XML result files. Default: target/inspection-results\n    #resultdir: target/inspection-results\n\n    # IDEA installation home directory. Default: IDEA_HOME environment variable or \"idea\".\n    # ideahome: /home/ben/devel/idea\n\n    # Limit IDEA inspection to this directory (This overrides scoping)\n    # dir: .\n\n    # Use this inspection profile file located \".idea/inspectionProfiles\".\n    profile: bentolor_2018.xml\n\n    # IDEA project root directory containing the \".idea\" directory\n    # rootdir: .\n\n    # Full path to the local idea.properties file. More info at:\n    # http://tools.android.com/tech-docs/configuration\n    # iprops: /Users/Shared/User/Library/Preferences/AndroidStudio2.1/idea.properties\n\n## Command line based usage\n\nFor a full / up-to-date list of options please run `idea-cli-inspector\n-h`:\n\n    = IntellIJ IDEA Code Analysis Wrapper - v1.5.2 - @bentolor\n\n    This tools runs IntelliJ IDEA inspection via command line and\n    tries to parse the output.\n\n    Example usage:\n      ./idea-cli-inspector -i ~/devel/idea -r . -p myinspections.xml \\\n         -d src/main/java -s unused,Annotator,TodoComment.xml -l ERROR\n\n    For more convenience you can pass all options in a `.ideainspect` file\n    instead of passing it via command line\n\n    usage: groovy idea-cli-inspector [options]\n     -d,--dir \u003cdir\u003e           Limit IDEA inspection to this directory.\n                              Overrides the scope argument.\n     -h,--help                Show usage information and quit\n     -i,--ideahome \u003cdir\u003e      IDEA or Android Studio installation home\n                              directory. Default: IDEA_HOME env var or `idea`\n     -ip,--iprops \u003cfile\u003e      Full path to your `idea.properties`. Only\n                              required if 1) you use --scope and 2) file is\n                              not located under in the default.\n                              Default: `\u003cideahome\u003e/idea/bin/idea.properties`\n     -l,--levels \u003clevel\u003e      Levels to look for. Default: WARNING,ERROR\n     -n,--dry-run             Dry-run: Do not start IDEA, but run parsing\n     -p,--profile \u003cfile\u003e      Use this inspection profile file. If given an\n                              absolute path, the target file is used,\n                              otherwise the arg denotes a file located under\n                              `.idea/inspectionProfiles`.\n                              Default: `Project_Default.xml`\n     -r,--rootdir \u003cdir\u003e       IDEA project root directory containing the\n                              `.idea` directory. Default: Working directory\n     -rf,--rootfile \u003cfile\u003e    full path to the pom.xml or build.gradle file\n                              for the project. Useful if the project is maven\n                              or gradle based and its rootdir does not contain\n                              all the *.iml and .idea/modules.xml files\n     -s,--skip \u003cfile\u003e         Analysis result files to skip. For example\n                              `TodoComment` or `TodoComment.xml`.\n     -sc,--scope \u003cstring\u003e     The name of the \"Custom scope\" to apply. Custom\n                              scopes can be defined in the IDE. Share the\n                              resulting file in .idea/scopes/scopename.xml and\n                              provide the name of the scope (not file) here.\n     -sf,--skipfile \u003cregex\u003e   Ignore issues affecting source files matching\n                              given regex. Example: `.*/generated/.*`.\n     -t,--resultdir \u003cdir\u003e     Target directory to place the IDEA inspection\n                              XML result files.\n                              Default: `target/inspection-results`\n     -v,--verbose             Enable verbose logging\n\n# Example usage\n\n    $ groovy idea-cli-inspector \\\n        -i ~/devel/idea \\\n        -r ~/projects/p1 \\\n        -p myinspections.xml \\\n        -d server \\\n        -s unused,Annotator,TodoComment.xml \\\n        -l ERROR\n\nThis looks for a IntelliJ installation in `~/devel/idea`, tries to\nperform a CLI-based code inspection run on the IDEA project\n`~/projects/p1/.idea` with an inspection profile\n`~/projects/p1/.idea/inspectionProfiles/myinspections.xml` limiting the\ninspection run to the subdirectory `server` within your project.\n\nThe IDEA inspection run will produce a set of `.xml` files. The amount,\nlevels and result is based on the inspection profile you passed. Option\n`-s` tells to skip \u0026 ignore the warnings contained in the inspection\nresult files `unused.xml`, `Annotator.xml` and `TodoComment.xml`. You\ncan ommit the `.xml` suffix for convenience.\n\nBy default it will then look for entries marked as `[WARNING]` or\n`[ERROR]` within the remaining inspection result report files. In our\ncase we only care for ERROR entries. If it finds entries, it will report\nthe file joined with a description pointing to the file location and the\ninspection rule.\n\n# Vanilla Maven and Gradle projects\n\nFor many maven and gradle-based projects, .iml files and xml files under\n`.idea/libraries` are not committed to SCM as they are generated by\nIntelliJ based on maven/gradle files (see\n\u003chttps://intellij-support.jetbrains.com/hc/en-us/articles/206544839-How-to-manage-projects-under-Version-Control-Systems\u003e\nafter \"You may consider not to share the following\").\n\nFor such projects, the inspection must be launched by passing the path\nto the maven/gradle project file like in the following example:\n\n    $ groovy idea-cli-inspector \\\n        --ideahome ~/devel/idea \\\n        --rootdir ~/projects/p1 \\\n        --rootfile ~/projects/p1/pom.xml\n        --profile ~/myinspections.xml \\\n        -l ERROR\n\n# Example output\n\n    ➜ idea-cli-inspector.git git:(master) ✗ ./idea-cli-inspector -i ~/devel/idea -r ../dashboard.git -p bens_idea15_2015_11.xml -d server -s Annotator,JSUnresolvedLibraryURL.xml,JavaDoc,TodoComment -l ERROR,WARNING\n\n    = IntellIJ IDEA Code Analysis Wrapper - v1.0 - @bentolor\n    #\n    # Running IDEA IntelliJ Inspection\n    #\n    Executing: /home/ben/devel/idea/bin/idea.sh [/home/ben/devel/idea/bin/idea.sh, inspect, /home/ben/projects/idea-cli-inspector.git/../dashboard.git, /home/ben/projects/idea-cli-inspector.git/../dashboard.git/.idea/inspectionProfiles/bens_idea15_2015_11.xml, /home/ben/projects/idea-cli-inspector.git/../dashboard.git/target/inspection-results, -d, server]\n    log4j:WARN No appenders could be found for logger (io.netty.util.internal.logging.InternalLoggerFactory).\n    log4j:WARN Please initialize the log4j system properly.\n    log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.\n    Please configure library 'Node.js v4.2.1 Core Modules' which is used in module 'client'\n\n       ...\n       IDEA spilling out quite a bunch of exceptions during inspection run\n       ...\n\n    #\n    # Inspecting produced result files in ../dashboard.git/target/inspection-results\n    #\n    # Looking for: [[WARNING], [ERROR]]\n    # Ignoring : [Annotator, JSUnresolvedLibraryURL, JavaDoc, TodoComment]\n    --- ClassNamePrefixedWithPackageName.xml\n    [WARNING] server/src/main/java/de/foo/dashboard/data/DatasetVerticle.java:28 -- Class name \u003ccode\u003eDatasetVerticle\u003c/code\u003e begins with its package name #loc\n    [WARNING] server/src/main/java/de/foo/dashboard/data/DatasetBuilder.java:17 -- Class name \u003ccode\u003eDatasetBuilder\u003c/code\u003e begins with its package name #loc\n\n    --- InterfaceNamingConvention.xml\n    [WARNING] server/src/main/java/de/foo/dashboard/constants/Events.java:11 -- Interface name \u003ccode\u003eEvents\u003c/code\u003e is too short (6 \u003c 8) #loc\n\n    --- SameParameterValue.xml\n    [WARNING] server/src/main/java/de/foo/dashboard/data/DatasetBuilder.java:30 -- Actual value of parameter '\u003ccode\u003etype\u003c/code\u003e' is always '\u003ccode\u003ede.exxcellent.dashboard.constants.DatasetType.ARRAY\u003c/code\u003e'\n\n    --- Skipping JavaDoc.xml\n    --- Skipping TodoComment.xml\n    --- DeprecatedClassUsageInspection.xml\n    [WARNING] server/pom.xml:99 -- 'io.vertx.core.Starter' is deprecated\n\n    --- Skipping JSUnresolvedLibraryURL.xml\n    --- Skipping Annotator.xml\n    --- unused.xml\n    [WARNING] server/src/main/java/de/foo/dashboard/data/DatasetBuilder.java:40 -- Method is never used.\n    [WARNING] server/src/main/java/de/foo/dashboard/constants/DatasetType.java:14 -- Field has no usages.\n    [WARNING] server/src/main/java/de/foo/dashboard/constants/DatasetType.java:14 -- Field has no usages.\n    [WARNING] server/src/main/java/de/foo/dashboard/data/DatasetVerticle.java:28 -- Class is not instantiated.\n    [WARNING] server/src/main/java/de/foo/dashboard/transformers/History.java:23 -- Class is not instantiated.\n\n    #\n    # Analysis Result\n    #\n    Entries found. return code: 1\n\n# Running within a Docker container (i.e. Travis CI)\n\nHere is a `.travis.yml` which demonstrates how to run\n`idea-cli-inspector` within a Docker container. You can see this in\npractice running [here on Travis\nCI](https://www.travis-ci.org/bentolor/microframeworks-showcase/) with\nthe source inspected [in my microframeworks-showcase\nproject](https://github.com/bentolor/microframeworks-showcase/)\n\nTwo things to note:\n\n  - IDEA needs some very basic configuration already existing. At least\n    i.e. the `.IntelliJIdea2018.1/config/options/jdk.table.xml` which\n    defines the locations of the installed JDKs\n\n  - The IDEA configuration directory location *varies from version to\n    version and edition to edition*. I.e. it’s `~/.IntelliJIdea2018.1`\n    for the IDEA 2018.1 Ultimate edition and `~/.IdeaIC2018.1` for the\n    community edition\n\n  - If you are using i.e. Node, Scala, VueJS etc. in your project please\n    note, that these plugins bring more inspections to the table. If you\n    want to have them in your CI/Docker run to, ensure that you add them\n    to i.e. `.IntelliJIdea2017.3/config/plugins/` directory so they are\n    picked up and effective.\n\n  - You can build these required configurations either by manually\n    adjusting and then copying those configuration file into the\n    container or by i.e. manually starting IDEA within the container\n    once with the configuration directories mapped as Docker volumes\n    i.e. like:\n\n\u003c!-- end list --\u003e\n\n    xhost si:localuser:root\n    docker run -it --rm \\\n               --dns 192.168.144.18 --dns 8.8.8.8 \\\n               -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix \\\n               -v `pwd`/root/.IntelliJIdea2018.1:/root/.IntelliJIdea2018.1 \\\n               -v `pwd`/root/.java:/root/.java  debug-ideacli-dockeragent  \\\n               /bin/bash\n\n    language: java\n\n    before_cache:\n      - rm -f  $HOME/.gradle/caches/modules-2/modules-2.lock\n      - rm -fr $HOME/.gradle/caches/*/plugin-resolution/\n\n    cache:\n      directories:\n        - $HOME/.gradle/caches/\n        - $HOME/.gradle/wrapper/\n\n    before_install:\n      - sudo add-apt-repository ppa:mmk2410/intellij-idea -y\n      - sudo apt-get update -q\n      - sudo apt-get install intellij-idea-community -y\n      - sudo apt-get install groovy -y\n\n    install:\n      - wget https://github.com/bentolor/idea-cli-inspector/archive/master.zip\n      - unzip master.zip\n      - sudo chmod -R aog+w /opt/intellij-idea-community/bin\n\n    script:\n      # Copy idea configuration template (mostly .IntelliJIdea2018.1/config/options/jdk.table.xml)\n      - cp -r ./tools/idea-cli-inspector/root/.IntelliJIdea2018.1 /home/travis/\n      # Duplicate for community config dir\n      - cp -r ./tools/idea-cli-inspector/root/.IntelliJIdea2018.1 /home/travis/.IdeaIC2018.1\n      - ./idea-cli-inspector-master/idea-cli-inspector -i /opt/intellij-idea-community\n\n# Troubleshooting \u0026 FAQ\n\n**My inspection runs very long and takes to much time. What can I do?.**\n\nFirst: Introduce and use a new scope where you exclude all folders\nand/or include only those folders which are relevant for your\ninspection. Typical folders which are not relevant are i.e.\n`node_modules`, `docs` or build output folders. Secondly think about\ncreating and using a custom inspection profile for the purpose of the\nCI. There you i.e. might disable all inspections with INFO/HINT level or\ni.e. the spell checking.\n\n**I receive a error message *Please, specify sdk 'null' for module\n'foo'*.**\n\nProbably you excluded `misc.xml` from the versionied IDEA project. Which\nis fine because this file is quite volatile. But this is the file where\nIDEA stores the \"Root JDK\".\n\nTo fix this error simply assign every module a SDK other than \"Project\nSDK\".\n\n**The analysis seems to produce different results on subsequent runs on\nthe same sources (esp. JavaScript).**\n\nThis seems to be an issue with the IDEA caches which IntelliJ keeps i.e.\nunder `.IntelliJ201X.X/system`. Try if deleting this directory prior to\nexecuting the analysis runs produces stable results.\n\n**What shall I pass as IDEA home directory for Mac OSX?.**\n\n`/Applications/IntelliJ\\ IDEA.app` should be the default installation\nfolder.\n\n**I’m using Android Studio and I can’t find `idea.properties`\\!.**\n\nSee the details about the location at\n\u003chttp://tools.android.com/tech-docs/configuration\u003e\n\n**Scoping does not work?.**\n\nFirst: Did you versionate the `.idea/scope/scopename.xml` file in your\nproject? Did you specify the Custom scope *name* and not the filename?\n\nIf no, it might be that there is an issue that you are not pointing the\n`--iprops` option to the right `idea.properties` file or you i.e. don’t\nhave write access for it.\n\n*Background information and troubleshooting:* Unfortunately IDEA yet\ndoes not offer a direct CLI option for applying scope. Therefore we need\nto pass a System property entries via modifying the `idea.properties`\nfile. Check the output of the script if you spot any issues during this\nprocess. Check the content of `idea.properties` during the run and look\nout for you scope name.\n\n**I receive different results in my IDE vs. on the CI server.**\n\nPlease check the following:\n\n  - ❏ Same version of IDEA installed on CI vs. you installation?\n\n  - ❏ Do you have the same plugins installed? Some bring own inspections\n    or support fur understanding file formats (like `.vue` files with\n    the vue plugin).\n\n  - ❏ Do you delete the `.IntelliJ201X.X/system` folder prior to every\n    run on CI (see above)?\n\n# Source code \u0026 Contributions\n\nThe source code is located under\n\u003chttps://github.com/bentolor/idea-cli-inspector\u003e.\n\n# License\n\nLicensed under the Apache License, Version 2.0 (the \"License\"); you may\nnot use this file except in compliance with the License.\n\nYou may obtain a copy of the License at\n\u003chttp://www.apache.org/licenses/LICENSE-2.0\u003e\n","funding_links":[],"categories":["Groovy"],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbentolor%2Fidea-cli-inspector","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fbentolor%2Fidea-cli-inspector","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbentolor%2Fidea-cli-inspector/lists"}