[bug] npm run script for testing missed from published package

[DerekNonGeneric]

This package is currently being flagged by Socket with a Severity: Medium issue due to a lack of tests. This is negatively impacting how its quality score is performing over there. To avoid getting flagged for this by Socket, the test property of the scripts object in the package.json file of our next releases need to contain the testing command for it to run. It seems to have been omitted even though we do actually have some tests (coverage is far from complete). The lack of coverage metrics is another story entirely.

It would be a good idea if we could include a check to ensure that our packages are published with this property specifying a shell command to run for testing. It may be worth noting that a non-zero exit code would equate to test failure according to CITGM, npmlog, and elsewhere, which is something to consider when determining the command.