I started to tweak the Audit node on Friday, with the intention of also including package info for each node. I am confident I have a workflow that will allow the package for each Node to be reported.
My only concern at the moment is that for identification to be successful the audit will need to be run on the script creators PC before being included in a distribution package containing the audit CSV and the DYN. This is because any reference to node package locations for data on which node is from where, can only be done if the packages are present with my old workflow.
Because there is no up to date full catalogue of dynamo nodes online for my workflow to reference this makes the next step interesting. Please correct me if I am wrong. (dynamonodes.com is good, hence What.the.node, but I have experienced gaps in it being up to date, and reporting of nodes is wrong packages eg Core nodes being from Zebra… )
Embedding the catalogue of nodes within the script is something I am also looking at, as well as tweaking efficiency on Monday. Fingers crossed