[Magisk] zgfg:
No, it crawls through directories and tests all json files it finds there, one by one.

Please open the script and read the comments at the top - certain scripting knowledge is required (or better to say, I have no time and willing to explain how to use it , and/or it was described in some earlier posts)

Eg:

DIR_DEPTH=4

defines that it will look for and test all json files it finds in the subfolders up to the sub-sub-sub-sub-folder level

You may need to tweak the other variables at the beginning of the script

Suggesting you to start testing with just a one or two JSON files, to see how it goes, how to set your own environment/process and what you need to tweak in the scrpt

__

Eg, I have PIF folder on Internal memory, with a subfolder Testing, and further subfolders.

Those subfolders contain the prepared/downloaded JSON files to be tested (my subfolders are eg named as Nokia/A8 and so, and that one contains eg JSON files for Nokia A8 phones, etc)

Then I execute the script directly from MiXplorer by selecting the script file and choosing Execute from the MiXPlorer menu. MiXPlorer must be granted root, it will execute the script with su grant, and script will start crawling from the PIF folder going down till the subfolders of the fourth level

Script is currently prepared for testing with PI Fork and you should have JSON files prepared for the Fork v8 format. However, script can be tweaked (look into the code and comment/uncomment lines) to be used with the PI Fix module instead.

Also, even the PI Fork (at some extent) can work with the more simple JSON formatted files, but some JSON files (intentionally, I will not go to the details) may fail to pass Device Integrity if not migrated in advance

---

Script can be also put to /adb/local/tmp with chmod a s executable, and then you can call it from Terminal Emulator like eg:

su -c /adb/local/tmp/pif-test-tbchecker.sh /sdcard/PIF

and the script will then crawl through the subfolders starting from the given /sdcard/PIF path

---

Be aware (comment out that line in the script if you don't like) that script automatically delets all JSON files that did not pass.

So it works like the Sieve of Eratosthenes - at the end, remaining are only those JSON files that passed, and easy to copy/save those JSON that passed)

Script also creates the pif.txt file with the list of all JSON files (with their full paths) that were tested, with their results.

During the test, you must not use the phone - script must execute Yasnac, SPIC/TB-Checker in the foreground - script cannot 'tap' the Test Play Integrity in eg SPIC and cannot grab the Meets or not results from the phone screen

Hence it may happen that you get a phone call while testing and script will continue to execute in the background but will not be able to manipulate Yasnac and SPIC/TB-Checker and read their results:

Those JSON files (not successfully tested) won't be deleted and in the pif.txt file you will see that they were not "Deleted" nor "MEET_DEVICE_INTEGRITY" but marked as "Inconcluive" - you can re-run the script to sieve them further

It can also happen that SPIC or TBChecker go out-of -quota (first of all, you can tweak the script to use one or another), in that case all files will be left (not deleted( but marked in pif.txt as "Inconclusive" - better stop the script (wasting time)when you see that API error -8 or so in SPIC or TB-Checker