Hi, I wonder if there exists something like a linter which can scan a patch or directory, looking for non-Vanilla objects and preferably saying which external library each belongs to?

When you're looking to check the portability of your patches, what do you use?

@baffalop I don't think so....... but vanilla will do the job.
Put a portable (non installed) version of vanilla in a folder on your desktop, open its binary (in the bin folder...... pd.exe for windows), and then open the patch from the terminal.
You will get a list of problems (including objects that will not create) in the terminal........
Hint.... set the log level to "1" in the terminal to see only errors, and then click each error to see which part of the patch it is from.....(highlighted objects in blue in the patch).....
David.

Another option would be to find the folder where all your externals are stored and temporarily rename it (ie. "externalss") so that PD can't find it. That way you'll get an error message for every broken object, as David said.

You could conceivably automate the process using [findbrokenobjects] in iemguts, but it would be difficult to identify which library each broken object comes from. There is a list here, but it's not up to date.

Thanks for the good suggestions.

To me, it sounds like a job for Python! https://github.com/baffalop/skrypts

Now includes searching of a Pd-extended path if provided.