Here is my revised node (to be distributed in package in the coming weeks)
Please note that I have only had the ability to test this on my systems architecture, so let me know if you get any different results.
- File Name
- File Size
- Workspace Version
- Total Connectors
- Unique Node Names, Types, Numbers and Packages (with versions if available)
- Node Types and Numbers
- Total Nodes
- Export Report to CSV
- Export an Audited DYN containing a code block listing Audit information.
(Both are placed in the same folder as the original DYN)
This node will only generate package information when used on the creators PC before distribution. This is due to the need to reference script nodes to package node locations locally. (This does mean that the run time for this node can be a little long, as it explores the contents of your package folder/s each time)
So to make users aware of required packages, the Audited DYN could be sent in lieu of the original as no other changes to the script are made apart from adding a code block full of text.
Special thanks to @awilliams for some super python scripting advice!
EDIT/UPDATE: FILE REMOVED, SEE POSTING BELOW FOR UP TO DATE FILE