That appears to be saying that the package will only run with that very old, and long out of support, version of nodejs. You have version 18, which is current, but it won't work with version 1 or above.
Welcome to the Forum. Since you are new here, I'll dig a bit deeper for you.
Not really. If it works for the "other guys," may be only because they are using seriously out-of-date software.
You can start troubleshooting this sort of thing by looking at the flows library page for the node. (Check the navigation bar at the top of this page.) You should notice right away that the node has not been updated in almost eight years. This might well be a record and almost guarantees that some later version of node.js or NodeRED will break it. If you follow the link to the GitHub repo, you will find open issues going back almost to the beginning, including one identical to yours involving NR version 2.0. The workaround proposed there (editing the package.json file) could allow the node to load, but I would very surprised if it actually works. If not, I'm afraid you're on your own to find an alternative.
I am running nodejs 18.14.2 and I get the ebadengine message but it appears that it treats it as a warning as the install does complete. You might like to upgrade to 18 to see if it works for you too.
You can do that, and upgrade to the latest node-red, using the install/upgrade script and adding --node18 to the end of the command.
Thanks for your tip. I was running the latest nodejs version so update had no effekt. I solved it by deleting the parameter 'Engine = strict' of the install sequence from the node.
I made a short test and it works