Just what the title says, I'm suggesting that if this tool detects Fractureiser, it outputs some nonzero exit code (different from one used for errors ideally), so that an automated build pipeline can use this to check a mod on compile (or periodically scan a system and alert if it's detected).
I'm asking bc I'd like to integrate this tool into the build pipeline for a mod of mine (not on CurseForge) just to be sure it doesn't get infected by e.g. a bad dependency and then I start putting out infected JARs without knowing it (if it can't spread this way, let me know too).
Another way would be some flag you can pass that makes it produce output easily parseable at the command line, the idea is just to make it easier to put this tool into automated pipelines or as a cron job to scan a system.
Edit: I might just make a PR for this, it shouldn't be that complicated.
Just what the title says, I'm suggesting that if this tool detects Fractureiser, it outputs some nonzero exit code (different from one used for errors ideally), so that an automated build pipeline can use this to check a mod on compile (or periodically scan a system and alert if it's detected).
I'm asking bc I'd like to integrate this tool into the build pipeline for a mod of mine (not on CurseForge) just to be sure it doesn't get infected by e.g. a bad dependency and then I start putting out infected JARs without knowing it (if it can't spread this way, let me know too).
Another way would be some flag you can pass that makes it produce output easily parseable at the command line, the idea is just to make it easier to put this tool into automated pipelines or as a cron job to scan a system.
Edit: I might just make a PR for this, it shouldn't be that complicated.
Edit 2: Made a PR (#59)