ok thanks, just wanted to let you know as the warning was mentioning 2 your plugins. I will happy ignore it now

npm audit report

form-data <2.5.4
Severity: critical
form-data uses unsafe random function in form-data for choosing boundary - https://github.com/advisories/GHSA-fjxv-7rqg-78g4
No fix available
node_modules/request/node_modules/form-data
request *
Depends on vulnerable versions of form-data
Depends on vulnerable versions of tough-cookie
node_modules/request

signalk-saillogger  *
Depends on vulnerable versions of request
node_modules/signalk-saillogger
signalk-windy  *

@Voodoo I don't really need to integrate my 2 old yanmar 4jh4 with the nav system.
Im happy with old fashioned analogue control panels, no need to monitor Bar and Celsius in NMEA or sailllogger. All I would like to achieve is engine status monitoring (running/not running) for trip's logs and statistic.
In my current setup I already have a Victron shunt for engines' alternators (separate 24v 110A alternators) that tiggers "motoring" path in SignalK when minimum 1 engine is running (and alternator charging the house batteries. I can also try using digital inputs of Cerbo to get on/off status control of each engine (we are a catamaran).

Works fine for me obviously for below surface (all other make no sense)

Dear Sailloger team
Thanks for implementing the support for NMEA engine monitoring.
In my boat I have old yanmars and won’t install analog to NMEA sensors due to the cost and difficulty of cabling 2 engines far from the NMEA backbone
Nevertheless I do have a monitoring of engine alternators current and based on ‘‘tis use auto state plugin to detect “motoring” status
Can sailloger monitor motoring status and log it in the trip data pus motoring hours?